Skip to main content
Skip table of contents

Appendix B – Ed-Fi Response Codes

Screenshot of Ed-Fi API Design and Implementation Guidelines, Response Codes page.  This page describes the codes that TEA would be expected to implement in their Ed-Fi SDK per Ed-Fi standards.

 Response and Status Codes

HTTP Response Code

Name

Reason(s)

200

OK

Returned after a successful operation when a response contains a body.

201

Created

Returned after a successful POST. The response from a POST will also include a location in the header pointing to the newly added resource. A POST response will not contain a body.

204

No Content

Returned when the server has fulfilled the request, but does not return an entity body.

304

Not Modified

Returned when the client includes the “If-None-Match” header containing the requested resource’s last known entity tag.

400

Bad Request

Returned if the request is malformed. The body of the response may contain a descriptive error message.

401

Unauthorized

Returned if the access token is invalid. The response will not contain a body.

403

Forbidden

Returned when the server is refusing to fulfill a request in situations such as the requesting client is not authorized to execute the requested action on the requested resource

404

Not Found

Returned if a resource is not found. The response will not contain a body.

409

Conflict

Returned when there is any type of referential integrity violation.

412

Precondition Failed

Returned if an “If-Match” header pre-condition fails.

500

Internal Server Error

Returned if the server encountered an unexpected error during the operation.

 

Note that a 403 error is most often caused by a dependency issue.  While DEX does internal dependency checks and withholds records from publishing where dependencies are identified, not all situations can be anticipated.  There will be cases where DEX attempts to publish a record that passed the internal dependency checks but was still rejected by the API because of a dependency.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.