Create network bulk feed

post

https://api.astrada.co/network-bulk-feeds

Registers a new feed for network bulk

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

network

string

enum

required

The network that the feed belongs

Allowed:

type

string

enum

Defaults to GL

The type of card network's bulk enrollment feed

Allowed:

networkReference

string

required

The identifier associated with the card network's bulk enrollment feed.
For Amex, this field should contain the Recipient ID in the following format 'R{RecipientId}', such as 'R123456'.
For Mastercard, this field should contain the Delivery ID.
For Visa-VBDS, this field should contain the RPIC in the following format 'RegionId_ProcessorId_IssuerId_CompanyId', such as '123_456_789_1'.
For Visa-VCF, this field should contain the RPIC in the following format 'RegionId_ProcessorId_IssuerId_CompanyId', such as '1_123_45_6789'; the region segment is ignored. The 3-segment PIC form 'ProcessorId_IssuerId_CompanyId', such as '123_45_6789', is also accepted.
For more details on our bulk enrollment process, refer to this guide.

subaccountId

uuid

required

The subaccount identifier

expectedCardCount

integer

1 to 1000000

The expected number of cards that will be enrolled under this bulk feed.
Optional. When provided, the value is echoed back on the response and on the
networkbulkfeed.statechanged webhook payload.

cardCount

integer

1 to 20

Defaults to 5

Sandbox only. The number of synthetic Visa cards to create when this
bulk feed is created in the sandbox environment. The cards are drawn
from the head of Astrada's published sandbox Visa test-card pool —
the same cards every feed, deduplicated once enrolled (matching the
cardCount field on the simulate-ingestion endpoints). Only valid
for type: VBDS feeds. Requests containing this field outside the
sandbox environment, or for any other feed type, are rejected with
a 400.

newCards

integer

1 to 20

Defaults to 5

deprecated

Deprecated alias of cardCount — use cardCount instead. When both
fields are provided, cardCount takes precedence. Same constraints
and behavior.

Headers

string

enum

Defaults to application/hal+json

Generated from available response content types

Allowed:

Responses

201Resource created

400The server cannot or will not process the request due to something that is perceived to be a client error

401Authentication credentials were either missing or incorrect

403Authentication credentials used do not have have permissions to perform the request

409Request conflict with the current state of the target resource

500The server encountered an unexpected condition that prevented it from fulfilling the request