Informational 1xx
| Error Code | Short Meaning | Informations |
| 101 | In progress. | The specified SyncML command is being carried out, but has not yet completed. |
Successful 2xx
| Error Code | Short Meaning | Informations |
| 200 | OK | The SyncML command completed successfully. |
| 201 | Item added | The requested item was added. |
| 202 | Accepted for processing | The request to either run a remote execution of an application or to alert a user or application was successfully performed. |
| 203 | Non-authoritative response | The request is being responded to by an entity other than the one targeted. The response is only to be returned when the request would have been resulted in a 200 response code from the authoritative target. |
| 204 | No content | The request was successfully completed but no data is being returned. The response code is also returned in response to a Get when the target has no content. |
| 205 | Reset content | The source should update their content. The originator of the request is being told that their content should be synchronized to get an up to date version. |
| 206 | Partial content | The response indicates that only part of the command was completed. If the remainder of the command can be completed later, then when completed another appropriate completion request status code SHOULD be created. |
| 207 | Conflict resolved with merge | The response indicates that the request created a conflict; which was resolved with a merge of the client and server instances of the data. The response includes both the Target and Source URLs in the Item of the Status. In addition, a Replace command is returned with the merged data. |
| 208 | Conflict resolved with client’s command "winning". | The response indicates that there was an update conflict; which was resolved by the client command winning. |
| 209 | Conflict resolved with duplicate | The response indicates that the request created an update conflict; which was resolved with a duplication of the client’s data being created in the server database. The response includes both the target URI of the duplicate in the Item of the Status. In addition, in the case of a two-way synchronization, an Add command is returned with the duplicate data definition. |
| 210 | Delete without archive | The response indicates that the requested data was successfully deleted, but that it was not archived prior to deletion because this optional feature was not supported by the implementation. |
| 211 | Item not deleted | The requested item was not found. It may have been previously deleted. |
| 212 | Authentication accepted | No further authentication is needed for the remainder of the synchronization session. This response code can only be used in response to a request in which the credentials were provided. |
| 213 | Chunked item accepted and buffered. | |
| 214 | Operation cancelled | The SyncML command completed successfully, but no more commands will be processed within the session. |
| 215 | Not executed | A command was not executed, as a result of user interaction and user chose not to accept the choice. |
| 216 | Atomic roll back OK | A command was inside Atomic element and Atomic failed. This command was rolled back successfully. |
Redirection 3xx
Originator Exceptions 4xx
| Error Code | Short Meaning | Informations |
| 401 | Unauthorized | insufficient rights to complete the command. |
| 407 | Authentication required | |
| 404 | N/A | No description available yet |
| 412 | Incomplete command | |
| 413 | Request entity too large | If the Search command results are too large for processing on the recipient |
| 415 | Unsupported media type or format | If the media type or format for the data item is not supported by the recipient |
| 420 | Device full | device storage is full |
| 423 | Soft-delete conflict | The requested command failed because the "Soft Deleted" item was previously "Hard Deleted" on the server. |
| 424 | Size mismatch. | The chunked object was received, but the size of the received object did not match the size declared within the first chunk. |
Recipient Exception 5xx
| 500 | Command failed | Non-specific error created by the recipient while attempting to complete the command |
