An optional “sneak preview” of our future API v1 error responses. This is provided to give integrators a chance to work with our future error codes. Error codes for the same error may change between v0 and v1.

A human-readable string explaining this particular error.

A human-readable string for this general category of error, which corresponds 1-to-1 with error types (title is the human-readable version of type). There can be multiple distinct titles for the same HTTP status code, and the same title can result in many different detail strings.
This field will be removed in API v1.

A machine-readable string that identifies the error for programmatic use. This is a URI, i.e. a globally unique identifier. It is not necessarily a URL, so do not expect it to resolve to a web page. You can use this whole string as an error code, or just everything after the last slash.
This field will be removed in API v1.

An optional “sneak preview” of our future API v1 error responses. This is provided to give integrators a chance to work with our future error codes. Error codes for the same error may change between v0 and v1.

A human-readable string explaining this particular error.

A human-readable string for this general category of error, which corresponds 1-to-1 with error types (title is the human-readable version of type). There can be multiple distinct titles for the same HTTP status code, and the same title can result in many different detail strings.
This field will be removed in API v1.

A machine-readable string that identifies the error for programmatic use. This is a URI, i.e. a globally unique identifier. It is not necessarily a URL, so do not expect it to resolve to a web page. You can use this whole string as an error code, or just everything after the last slash.
This field will be removed in API v1.

An optional “sneak preview” of our future API v1 error responses. This is provided to give integrators a chance to work with our future error codes. Error codes for the same error may change between v0 and v1.

A human-readable string explaining this particular error.

A human-readable string for this general category of error, which corresponds 1-to-1 with error types (title is the human-readable version of type). There can be multiple distinct titles for the same HTTP status code, and the same title can result in many different detail strings.
This field will be removed in API v1.

A machine-readable string that identifies the error for programmatic use. This is a URI, i.e. a globally unique identifier. It is not necessarily a URL, so do not expect it to resolve to a web page. You can use this whole string as an error code, or just everything after the last slash.
This field will be removed in API v1.

An optional “sneak preview” of our future API v1 error responses. This is provided to give integrators a chance to work with our future error codes. Error codes for the same error may change between v0 and v1.

A human-readable string explaining this particular error.

A human-readable string for this general category of error, which corresponds 1-to-1 with error types (title is the human-readable version of type). There can be multiple distinct titles for the same HTTP status code, and the same title can result in many different detail strings.
This field will be removed in API v1.

A machine-readable string that identifies the error for programmatic use. This is a URI, i.e. a globally unique identifier. It is not necessarily a URL, so do not expect it to resolve to a web page. You can use this whole string as an error code, or just everything after the last slash.
This field will be removed in API v1.