Asks Astrada to confirm that a card program can join a network bulk feed. Astrada checks with the issuing bank and the network by hand, then emails the card program admin with the answer. Unlike POST /network-bulk-enrollments, this is not a kickoff: it does not start outreach to the bank and can never be linked to a feed. A validation failure or an unknown subaccount answers 400, as for the kickoff.
A program has one open confirmation request at a time. A program is the calling account, the subaccountId, the network and the bin. Every stored request is open for 30 days from its createdAt, as nothing closes a request yet. When the program already has an open request that another request wrote, this request stores nothing and answers 200 with that request's summary (alreadyOpen: true), whatever new requestId it sent. No second request reaches Astrada. Two requests for one program sent at the same time store one request between them.
Once a request is 30 days old it stops holding its program: nothing is written to it, and the next request for the program is stored with 201 and reaches Astrada again.
The route answers these errors as application/problem+json, with title and detail:
| Status | When | detail |
|---|---|---|
400 | The body does not pass validation. errors lists each field that failed. | Request parameters are invalid |
400 | subaccountId is not a subaccount of the calling account. | The subaccount {subaccountId} was not found |
403 | The token holds neither network-bulk-enrollments:write nor network-bulk-feeds:write. | You do not have permission to access the requested resource |
500 | The request could not be completed. | An unexpected error occurred or The server encountered an unexpected condition that prevented it from fulfilling the request |
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
