Authenticator Private Issue Access API

This API is used to provide users with issues that unregistered users cannot see. Through this API it is also possible to implement per-user issue lists.

You should use this API to control exactly which issues a user sees, based on the receipt that is passed.

This API is different to the Verify API and requires it's own URL.

Implementation

The API will be sent an HTTP POST request containing the list of iTunes product IDs of private issues. It returns a JSON payload containing the iTunes product ids that should be provided to the user.

Method: POST
Params: receipt, text
        issues, comma-separated list of iTunes product ids

Return format: JSON Required Keys: issues: array of iTunes product ids, possibly empty. For example, the authenticator should be able to be hit via curl like so:

curl -H 'Accept: */*; q=0.5, application/xml' -d "receipt=abc123" -d "issues=com.your.issue.one,com.your.issue.two,com.your.issue.three" http://your-app.com/your-authenticator/api/issues

And return a response body similar to:

{ "issues": ["com.your.issue.one", "com.your.issue.three"] }

This will provide access only to the private issues with an iTunes product ID of: com.your.issue.one and com.your.issue.three

N.B. the accept header in the above curl example is there to emulate the actual headers that the Oomph backend will send. Due to historical reasons it requests a wildcard content type with a preference for XML. The API should return a JSON payload and not XML. (This pattern may change in future but is current as of July 2015)

Got a question? Ask a question to the Oomph Community or submit a new Support request.