- Aurora Rest API
- End Points
- Account Details
- All Assets
- Data for Account
- All Effects
- Effects for Account
- Effects for Ledger
- Effects for Operation
- Effects for Transaction
- All Ledgers
- Ledger Details
- Metrics
- Offers for Account
- All Operations
- Operations for Account
- Operations for Ledger
- Operations for Transaction
- Operation Details
- Orderbook Details
- Find Payment Paths
- All Payments
- Payments for Account
- Payments for Ledger
- Payments for Transaction
- Trade Aggregations
- Trades for Account
- Trades for Offer
- Trades
- All Transactions
- Post Transaction
- Transactions for Account
- Transactions for Ledger
- Transaction Details
- Resources
- Errors
- HC NET APIs >
- Errors >
- Bad Request
Bad Request
Bad Request
If Aurora cannot understand a request due to invalid parameters, it will return a bad_requesterror. This is analogous to the HTTP 400 Error.
If you are encountering this error, check the invalid_field attribute on the extras object to see what field is triggering the error.
Attributes
As with all errors Aurorare turns, bad_request follows the Problem Details for HTTP APIs draft specification guide and thus has the following attributes:
| Attribute | Type | Description |
|---|---|---|
| Type | URL | The identifier for the error. This is a URL that can be visited in the browser. |
| Title | string | A short title describing the error. |
| Status | Number | An HTTP status code that maps to the error. |
| Detail | string | A more detailed description of the error. |
| Instance | string | A token that uniquely identifies this request. Allows server administrators to correlate a client report with server log files |
Evelyn
Support Agent
*Powered by HashCash