To use Destination SDK, make sure that you meet the technical and partnership prerequisites listed in the sections below.
Technical / API prerequisites for streaming destinations
You have a REST API endpoint for Adobe Experience Platform to deliver the following types of data to:
Segment membership information;
Profile identity information;
(Optional) Additional attributes for profile enrichment.
Your REST API endpoint supports API token bearer authentication or the OAuth 2.0 authentication protocol.
(Optional) You have a segment create/update/delete API or API endpoint for programmatic metadata management.
Technical prerequisites for batch destinations
You have a destination location hosted on Amazon S3, Azure Blob, Azure Data Lake Storage, SFTP, Google Cloud, or a private Data Landing Zone, where you can receive files exported out of Experience Platform.
Your destination platform can ingest files in the format configured via the file formatting options in Destination SDK for batch destinations.
(Optional) You have a segment create/retrieve/update/delete (CRUD) API or API endpoint for programmatic metadata management.
If you are an Independent Software Vendor (ISV) or System Integrator (SI) looking to use Destination SDK, read the partnership requirements for ISVs and SIs in the getting access section.