This is a list of API endpoints that will enable you to monitor your data that is being accessed by the data subscribers.
List Subscribers
/contrib/subscribers #GET
A logged-in contributor can request a list of all subscribers that get data (partially) through their API.
Example:
- Contributor representative/developer logs-in (obtain auth token to api.mybitdoor.com).
- Call api.mybitdoor.com/contrib/subscribers, passing the token received in Step 1.
- See a list of Pentadata’s subscribers (name only) whose requests have been resolved with the help of this contributor.
GET consent
/contrib/consent/ #GET
A logged-in contributor can request the opt-in, opt-out dates of a given subscriber (must know subscriber-id).
LIST consent
/contrib/consent #GET
A logged-in contributor can request the opt-in, opt-out dates of all subscribers that are using their API.
LIST requests
/contrib/requests #GET
A logged-in contributor can request a list of all requests that we (mybitdoor/pentadata) made to get data through their API.
LIST merchants
/contrib/merchants #GET
A logged-in contributor can request a list of all merchants that have gotten data through mybitdoor, via this contributor’s API.
LIST cards
/contrib/card #GET
A logged-in contributor can request a list of cards (last four, expiration date) that we have enrolled with them.
LIST bank accounts
/contrib/account #GET
A logged-in contributor can request a list of bank accounts that we have enrolled with them.
**The bank accounts will be shown with a unique ID that is randomly generated from our
systems. This unique ID is used only on our platform and does not contain any unique
information that can be tied to the original bank account
LIST locations
/contrib/location #GET
A logged-in contributor can request a list of merchant’s locations that we have enrolled with them.