Bulk Endpoint

post

https://api.bavest.co/v2/bulk

Fan out a single endpoint across up to 100 symbols or ISINs in one request. Each entry is invoked concurrently against the target Lambda and results are returned as an array in the same order as the input.

Provide exactly one of symbols or isins. The params object is merged into every invocation for shared parameters (e.g., currency, date range).

Body Params

Bulk invocation request with symbols/ISINs, target endpoint, and optional shared parameters.

symbols

array of objects

required

length ≤ 100

List of per-symbol parameter objects. Each object is merged with params and sent to the target endpoint. Provide exactly one of symbols or isins.

symbols*

isins

array of objects

length ≤ 100

List of per-ISIN parameter objects. Each object is merged with params and sent to the target endpoint. Provide exactly one of symbols or isins.

isins

endpoint

string

enum

required

Target endpoint key. Determines which Lambda is invoked for each entry.

params

object

Additional parameters passed to every invocation. Merged with each symbol/ISIN entry. Use for shared parameters like date ranges.

Headers

string

enum

Defaults to application/json

Response content type. Only application/json is supported.

Allowed:

Responses

Language

Credentials

Header

URL

Request

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response

400Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive).

401Missing or invalid API key.

404Resource not found.

429Rate limit exceeded. Retry after the Retry-After header interval.

500An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.

502Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay.

504The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load.

defaultAn unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.