Create network bulk confirmation

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:

StatusWhendetail
400The body does not pass validation. errors lists each field that failed.Request parameters are invalid
400subaccountId is not a subaccount of the calling account.The subaccount {subaccountId} was not found
403The token holds neither network-bulk-enrollments:write nor network-bulk-feeds:write.You do not have permission to access the requested resource
500The request could not be completed.An unexpected error occurred or The server encountered an unexpected condition that prevented it from fulfilling the request
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
uuid
required

Your idempotency key for this confirmation, unique per account. Repeating the request with a requestId that was already used returns the stored confirmation, whole and unchanged, with 200 instead of creating a second one with 201. A new requestId for a program that already has an open request answers 200 with that request's summary.

uuid
required

The subaccount the card program belongs to. Must belong to the calling account; an unknown subaccount answers 400.

string
enum
required

The network of the card program.

Allowed:
string
required
^[0-9]{8}$

Exactly the first 8 digits of the card number. Never send the full card number.

string
enum

The bulk likelihood grade your client saw for this BIN, as returned in bulkLikelihood by POST /enrollment-methods. Send it whenever that response had one. Leave it out (or send unchecked) only when the response had no bulkLikelihood because it could not be determined; the request is then stored as unchecked.

Allowed:
binInfo
object

Optional. The issuer details shown to the person who asked for the confirmation, in the GET /bin-lookup vocabulary. Stored as a display snapshot only; every field is optional.

company
object
required
cardAdmin
object
required

The card program administrator. Astrada emails this person with the answer.

bankContact
object

Optional. The company's relationship contact at the issuing bank.

string
length between 1 and 100

Optional. Your own id for this confirmation, echoed back on the resource.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json