Status Codes | RESTful API | Teradata Data Mover - RESTful API Status Codes - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.10
Published
June 2021
Language
English (United States)
Last Update
2021-06-16
dita:mapPath
fcu1619423186706.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
One of the following HTTP status codes is returned in response to a RESTful API call:
Code Definition Description
200 OK Request has succeeded.
201 Created Request has been fulfilled and a new resource is being created.
301 Moved Permanently Requested URL has been moved permanently and should be redirected. User the 'location' header to redirect.
400 Bad Request Request could not be understood by the server due to malformed syntax.
401 Unauthorized Request requires user authentication.
404 Not Found Resource referenced by the specified URL was not found.
409 Conflict Request could not be completed due to a conflict with the current state of the resource.
412 Precondition Failed Request could not be completed due to invalid input parameter.
500 Internal Server Error Data Mover service encountered an unexpected condition that prevented it from fulfilling the request.
If the API returns an error code (codes 400–500), the response body will contain a response parameter message with an explanation of the error.