{"_id":"57f45c62dd4d030e00974439","parentDoc":null,"project":"55de06fa57f7b20d0097636b","category":{"_id":"57dc1bbd3ed3450e00dc9ea7","__v":0,"project":"55de06fa57f7b20d0097636b","version":"55de06fa57f7b20d0097636e","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-09-16T16:20:13.682Z","from_sync":false,"order":7,"slug":"partner-attributes-api","title":"Data Marketplace API"},"user":"55de06e19db51a0d0064947d","__v":1,"version":{"_id":"55de06fa57f7b20d0097636e","project":"55de06fa57f7b20d0097636b","__v":14,"createdAt":"2015-08-26T18:35:38.642Z","releaseDate":"2015-08-26T18:35:38.642Z","categories":["55de06fb57f7b20d0097636f","55f1962e3936d52d00fb3c8f","55f1970339e3e8190068b2b8","55f1970d229b772300779a1f","55f1971cfd98c42300acc605","55f1d5c7fd98c42300acc69f","563cbfe4260dde0d00c5e9d4","5644cf437f1fff210078e690","57dc1bbd3ed3450e00dc9ea7","58a600a2243dd30f00fd8773","58ed1bdc068f780f00f64602","58f13b3a4f0ee50f00e24e81","58f173f792f9020f009cad16","591b42f8e633fd0f00077c5a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-05T01:50:26.478Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"The Data Marketplace API is provided as a way for PushSpring to ingest partner data and make it available for PushSpring Audience Console customers to use when building custom segments.\n\nThe API allows a data partner to define a set of Attributes associated with mobile advertising identifiers (IDFA and Google Play Ad Id are currently supported).  Each of these Attributes can be thought of as segments or tags *associated* with a set of device identifiers; users on the PushSpring Audience Console can then incorporate these Attributes into the custom segments they build.\n\nIt is critically important to work with PushSpring to decide on which Attributes to make available from your data set.  Each Attribute must be given a name and a description, both of which will be seen by Audience Console users.  \n\nFor each Attribute, you will use the APIs described on the Attribute documentation page to first declare the Attribute to PushSpring, setting all the necessary metadata.  You do this one time, and can update, remove, or create new Attributes over time as neeeded.\n\nOnce you have created the Attributes on our platform, you can proceed to creating data files that tell PushSpring which advertising identifiers should be associated with each attribute (see the File Format section for details).  Once your data files are ready for ingestion, you will upload them to an Amazon S3 bucket whose credentials PushSpring will supply to you, and then use the Import API to tell PushSpring to ingest.  You can also use APIs to check on ingestion status at the file level or at the Attribute level.\n\nWe hope you find this API straightforward to use.  Please reach out to your PushSpring contact with any questions.\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Authentication\"\n}\n[/block]\nAll authentication to the API is done via an API key that is issued to each partner.  The API key must be included as part of an Authorization header in the format of a Bearer token.\n\nAuthorization: Bearer <apikey>\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Request Access\"\n}\n[/block]\nFor access to the API please email hello:::at:::pushspring.com.","excerpt":"","slug":"ingestion-api-overview","type":"basic","title":"Overview"}
The Data Marketplace API is provided as a way for PushSpring to ingest partner data and make it available for PushSpring Audience Console customers to use when building custom segments. The API allows a data partner to define a set of Attributes associated with mobile advertising identifiers (IDFA and Google Play Ad Id are currently supported). Each of these Attributes can be thought of as segments or tags *associated* with a set of device identifiers; users on the PushSpring Audience Console can then incorporate these Attributes into the custom segments they build. It is critically important to work with PushSpring to decide on which Attributes to make available from your data set. Each Attribute must be given a name and a description, both of which will be seen by Audience Console users. For each Attribute, you will use the APIs described on the Attribute documentation page to first declare the Attribute to PushSpring, setting all the necessary metadata. You do this one time, and can update, remove, or create new Attributes over time as neeeded. Once you have created the Attributes on our platform, you can proceed to creating data files that tell PushSpring which advertising identifiers should be associated with each attribute (see the File Format section for details). Once your data files are ready for ingestion, you will upload them to an Amazon S3 bucket whose credentials PushSpring will supply to you, and then use the Import API to tell PushSpring to ingest. You can also use APIs to check on ingestion status at the file level or at the Attribute level. We hope you find this API straightforward to use. Please reach out to your PushSpring contact with any questions. [block:api-header] { "type": "basic", "title": "Authentication" } [/block] All authentication to the API is done via an API key that is issued to each partner. The API key must be included as part of an Authorization header in the format of a Bearer token. Authorization: Bearer <apikey> [block:api-header] { "type": "basic", "title": "Request Access" } [/block] For access to the API please email hello@pushspring.com.