Protocol sandbox
The register of every being of the three worlds, by the oldest rule.
Your tasks
A code appears when a task is done – type it into the lesson.
Tasks check what you did, so they need your account.
The Chronicle – SOAP
A SOAP 1.1 service with a WSDL: read the twenty sealed records without signing in, then create, replace and delete records of your own with HTTP Basic, a token from Login, or a WS-Security UsernameToken.
| Operation | Credentials | What it does |
|---|---|---|
Login | – | Your sandbox username and password → token (valid 3600 seconds) and expiresIn. |
GetCreature | no | One record by id. Records 1–20 are sealed and readable by everyone; yours are visible only to you. |
ListCreatures | no | Filters world, type, status, nameContains, sealed (combined with AND), limit 1–100 (default 20), offset. Answers total and one page. |
CreateCreature | yes | A new record of yours (no id, sealed or createdAt – the server sets them). |
UpdateCreature | yes | Replaces the whole record: an optional element you leave out returns to its default. |
DeleteCreature | yes | Deletes one of your records. A deleted id never comes back. |
| faultcode | Code in the detail | When |
|---|---|---|
| Client | CHR-INVALID-XML | The body is not well-formed XML. |
| Client | CHR-INVALID-REQUEST | An element breaks the schema: missing, unexpected, out of range, not in the list, Header after Body. |
| Client | CHR-UNKNOWN-OPERATION | The operation or its namespace is not in the WSDL. |
| Client | CHR-ACTION-MISSING | No SOAPAction header. |
| Client | CHR-ACTION-MISMATCH | The SOAPAction header names another operation. |
| Client | CHR-CONTENT-TYPE | Content-Type is not text/xml. |
| Client | CHR-UNAUTHENTICATED | No credentials, or a wrong username or password. |
| Client | CHR-TOKEN-INVALID | The token is malformed, signed wrongly or expired. |
| Client | CHR-NOT-FOUND | No such record for you (missing, deleted or someone else's). |
| Client | CHR-SEALED | Records 1–20 cannot be changed or deleted. |
| Client | CHR-LIMIT-REACHED | You keep 200 records at most. Reset my data clears them. |
| Server | CHR-INTERNAL | Something failed on the server. |
| MustUnderstand | CHR-MUST-UNDERSTAND | A header block with mustUnderstand="1" the service does not know. |
| VersionMismatch | CHR-SOAP-VERSION | A SOAP 1.2 envelope. Use SOAP 1.1. |
How to call it from your tools
GetCreature – request body
GetCreature with curl
CreateCreature with HTTP Basic
Login – request body
The token from Login in the SOAP Header
WS-Security UsernameToken (PasswordText) in the SOAP Header
An expired token, to see the fault (it belongs to no one)
The Chronicle keeps a record of every being of Yav, Nav and Prav. Read any record, write your own with your sandbox account, and meet every kind of SOAP fault on the way. The old records are sealed; yours are yours alone.
Addresses
Sign in on the right first: most calls need your token- SOAP endpoint
- SOAP contract (WSDL)
- REST base URL – sign-in, orders, keys