POST /v1/state/acs
Deprecated. Please use /v2/state/acs instead. The only difference with this endpoint and that one is the type of the after/next_page_token pagination token. Returns the ACS in creation date ascending order, paged, for a given migration id and record time. Unlike /v0/state/acs, every contract is identified by an (optional) update_id (as opposed to the event ID in /v0/state/acs, which was not BFT-safe).
Deprecated. Please use /v2/state/acs instead. The only difference with this endpoint and that one is the type of the after/next_page_token pagination token. Returns the ACS in creation date ascending order, paged, for a given migration id and record time. Unlike /v0/state/acs, every contract is identified by an (optional) update_id (as opposed to the event ID in /v0/state/acs, which was not BFT-safe).
Body
integer (int64).The migration id for which to return the ACS.string (date-time).The timestamp at which the contract set was active. This needs to be an exact timestamp, i.e., needs to correspond to a timestamp reported by /v0/state/acs/snapshot-timestamp if record_time_match is set to exact (which is the default). If record_time_match is set to at_or_before, this can be any timestamp, and the most recent snapshot at or before the given record_time will be returned.exact, at_or_before.integer (int64).Pagination token for the next page of results. For this to be valid, this must be the next_page_token from a prior request with identical parameters aside from after and page_size; the response may be invalid otherwise.integer (int32).The maximum number of created events returned for this request.Responses
200
okrecord_time as in the request.migration_id as in the request.page_size contracts in the ACS. create_arguments are always encoded as compact_json.after to the AcsRequest or HoldingsStateRequest. Will be absent when there are no more pages.400
bad request404
not found500
internal server errorHistory
0.7.50.7.5The POST /v1/state/acs operation changed in this snapshot.
0.6.0