You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 29, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: site/docs/messaging/campaign-management/imports/imports-api.mdx
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,9 +45,9 @@ This walks through how to programmatically import and view your campaigns _via A
45
45
46
46
## Important Notes
47
47
48
-
* We only allow imports for campaigns that have been approved by all carriers participating through TCR.
49
-
While provisioning your campaigns through your CSP, make sure to provision with all participating carriers.
50
-
If you are registering as your own CSP, exclude the 'mnoIds' property on the TCR CSP /campaigns/campaignBuilder endpoint request body.
48
+
* We only allow imports for campaigns that have been approved by all carriers participating through TCR.
49
+
While provisioning your campaigns through your CSP, make sure to provision with all participating carriers.
50
+
If you are registering as your own CSP, exclude the 'mnoIds' property on the TCR CSP /campaigns/campaignBuilder endpoint request body.
51
51
If you do not provision to all carriers, you will have to either work with TCR to remedy or create another campaign in which both campaigns will be subject to fees.
52
52
* If you get a '403 Unauthorized' error response while making an HTTP Request to any of the Import endpoints,
53
53
you will need to reach out to the Implementation team to get the Campaign Management role assigned to your API User.
0 commit comments