Create ExportDestination
Create a new Export Destination to use for your Data Export Schedules or Ad-Hoc Data Exports.
Currently, two options for setting up Data Export Destinations are available:
- S3 buckets on your AWS account.
- Buckets in your Google Cloud Storage account.
Request and Response schema:
- Use the selector under the destinationType parameter to expose the relevant request and response schema for the type of Destination.
Request and Response samples:
- Use the Example selector to show the relevant request and response samples for the type of Destination.
Path parameters
UUID of the organization
Request body
Response
Returns the created Export Destination.
Changes
Changed in 3 of the 10 revisions of this API.5109
- ▲
removed from the request body
oneOflistrequest-body-one-of-removed
- ○
added to the request body
anyOflistrequest-body-any-of-added
- ○
added request discriminator
request-body-discriminator-added
- ○
added to the response body
anyOflist for the response statusresponse-body-any-of-added
- ○
added response discriminator for the response status
response-body-discriminator-added
- ○
removed from the response body
oneOflist for the response statusresponse-body-one-of-removed
This revision also has 53 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
added the new required request property
////new-required-request-property
- ▲
added the new required request property
////new-required-request-property
- ▲
the request's body type changed from
objectto no typerequest-body-type-changed
- ▲
the response's body type changed from
objectto no type for statusresponse-body-type-changed
- ●
removed from the request body
allOflistrequest-body-all-of-removed
- ●
removed
subschema #3from the///request propertyallOflistrequest-property-all-of-removed
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ○
added the new optional request property
////new-optional-request-property
- ○
added the new optional request property
////new-optional-request-property
- ○
removed from the response body
allOflist for the response statusresponse-body-all-of-removed
- ▲
- ○
endpoint added
endpoint-added
This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○