adobe / experience-platform-postman-samples Goto Github PK

Expected Behaviour

In the /apis/readme.md it says to use the Adobe I/O Access Token Generation.postman_collection.json to gain an access token. It looks like this file no longer exists in the repo.

Actual Behaviour

Clicking the link in this readme takes me to a broken link. I can't find the actual file I need.

Steps to Reproduce

1.) Go to https://github.com/adobe/experience-platform-postman-samples/tree/master/apis

2.) Click the link under the "Access Token" header named Adobe I/O Access Token Generation.postman_collection.json.

Please note that the solution isn't deleting the link from the Readme. It's providing access to the collection. I really need this for what I'm working on at the moment.

@tsilver WDYT about creating a zip file of all the JSON files in, https://github.com/adobe/experience-platform-postman-samples/tree/master/apis/experience-platform and committing it to Git (in the same folder)?

This would be easy enough to do during the Swagger -> Postman Collection generating process and would provide a single-file download to get the latest set of Postman Collections.

Alternatives

Combining the existing Collections for AEP APIs into a single "Uber" postman collection would probably be a difficult/time-consuming and require significant changes to the Swagger -> Postman converter (ie. significant enough where I don't have the time to do them :))

The Segmentation API - Postman Collection is missing "Audiences" , is there plan to add it - https://github.com/adobe/experience-platform-postman-samples/tree/master/apis/experience-platform is missing https://developer.adobe.com/experience-platform-apis/references/segmentation/#tag/Audiences

In Postman 10.7.1 for MacOS, pm.request.headers.each() in the pre-request script fails when removing headers while iterating over them:

TypeError: Cannot read properties of undefined (reading 'value')

See details provided in #61.

Expected Behaviour

Call should be made successfully with the included accept header

Actual Behaviour

The current included accept header for the Retrieve a schema call is "application/vnd.adobe.xed-id+json"
When making a call with this header, the response is:
{
"type": "http://ns.adobe.com/aep/errors/XDM-1007-400",
"title": "Accept header invalid",
"status": 400,
"report": {
"registryRequestId": "d3c91881-5726-4c3a-aae1-a28ecb1a6b9d",
"timestamp": "06-24-2022 04:12:19",
"detailed-message": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)",
"sub-errors": []
},
"detail": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)"
}

I was able to get a good response by updating the Accept header to:
application/vnd.adobe.xed+json; version=1

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Download the Schema Registry API collection.
Make a call using "Retrieve a schema" and the included Accept header

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

should be jsrsasign-js

Expected Behaviour

Have examples of how to use the API to manage Audience Compositions

Actual Behaviour

Currently, there aren't examples of how to use the API to manage Audience Compositions

Reproduce Scenario (including but not limited to)

How to create and remove Audience Compositions by API

Steps to Reproduce

Platform and Version

AEP

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

The Create a query in QueryService API is supposed to allow to create and execute a new query by just importing the postman json files and sending the API request (where no additional headers need to be added).

Actual Behaviour

Even with all the required params and request body, the API fails with an authentication error.

The other requests in this collection work fine, this particular request is missing the Authorization header.

Reproduce Scenario

Download and import the postman file for the Query Service API. When you try to send the request for Create a query API, it fails with the above mentioned error.

Fix

Adding the Authorization header to this request solves the issue.

Make sure it matches the docs and the JWT blog post.

https://medium.com/adobetech/using-postman-for-jwt-authentication-on-adobe-i-o-7573428ffe7f

Hi, while testing the Policy Service API we found out that some of the documentation refers to dulePolicy and some to dulepolicy. The camelcase version gives an 404 - not found.

The swagger basePath refers to the non working camelcase version and the top on the API documentation webpage refers to the working one, non-camelcase version.

https://raw.githubusercontent.com/AdobeDocs/experience-platform-apis/main/src/swagger-specs/policy-service.yaml
https://developer.adobe.com/experience-platform-apis/references/policy-service/

Actual Behaviour

The current collection only deals with DULE for Datasets and not the basic operations related to datasets themselves as listed below.

Expected Behaviour

Dataset Service API collection should have the POST , GET and PATCH requests to list, create dataset, check and enable/disable the dataset for Profile (and upsert).

Recommendation

Within Dataset Service API there should be two folders- 'Datasets' , and 'DULE' [just like Schema Registry API has sub folders]

I have created and tested the requests above which should be part of basic 'Datasets' folder and request you to incorporate them into the official collection for this API and move the existing ones to the DULE subfolder.
[proposed] Dataset Service API.postman_collection.zip

ex. from @tsilver - "There are some issues we want to fix like the Schema creation needs to add the Immutable tag"

I believe this is updated in the L778 repo https://git.corp.adobe.com/dumlao/Summit-2019