API v.1 for Galaxy Gateway PEPPOL SMP
To be able to use this API, you need an SMP user account.
This API allows you to seamlessly integrate with Galaxy Gateway SMP to manage all your PEPPOL receivers instantly from within your own applications.
Please refer to the API specification and the WSDL to get you on track using the SMP API.
API URL: https://api.galaxygw.com via HTTP/SSL
Token: regular token or HMAC
The API is an add-on service and is priced separately. You can test the API by creating a token from within your account. Please be reminded that we might remove your token without prior notice if you use the API in production scenarios without letting us know about it.
To be able to use the API you need to create a token which is used for authentication. Select the token type that fits you best, either the regular token or the HMAC.
- Login to your user account.
- Click “Settings”
- Click “Create” under “Manage API Security Tokens”
SMP API v.1 Error Codes
If you want the v.2 error codes, please visit https://www.galaxygw.com/support/smp-api-error-codes.
|Error code||Error description|
|GGW-300||The value MUST have content, empty or null sequence is not allowed.|
|GGW-301||Requested ContentType was not available or could not be determined.|
|GGW-303||The specified media type is not supported|
|GGW-304||The supplied payload could not be interpreted as valid XML according to the XSD.|
|GGW-305||There were no ParticipantIdentifiers found to process.|
|GGW-306||The schema identifier used is not known.|
|GGW-307||Found a duplicated value of a ParticipantIdentifier, only the first occurrence will be processed.|
|GGW-308||A participant identifier value must consist of 4 numerals followed by a comma and an alphanumeric sequence.|
|GGW-309||The used participant type identifier is not supported.|
|GGW-310||The participant identifier you are trying to modify already belongs to another organization.|
|GGW-311||No participant identifier value available.|
|GGW-312||A fully qualified participant identifier value must be specified, e.g. |
|GGW-313||The participant identifier is not known.|
|GGW-314||There were no Endpoints found to process.|
|GGW-315||The endpoint id must be a positive integer.|
|GGW-316||An unsupported transport profile was used.|
|GGW-317||A valid URL must be given for endpoint address.|
|GGW-320||Certificates must be provided in PEM format.|
|GGW-321||Service description must be specified.|
|GGW-322||Technical contact url must be specified.|
|GGW-323||Technical information url must be specified.|
|GGW-324||No endpoint id available.|
|GGW-325||The submitted JSON content seems to be not well-formed.|
|GGW-326||Date must be well-formed according to ISO 8601.|
|GGW-327||The endpoint id is not known.|
|GGW-328||No metadata profiles were found.|
|GGW-329||The metadata profile id is not known.|
|GGW-330||A required field was not available.|
|GGW-350||There seems to have been a problem when trying to obtain the data stream.|
|GGW-360||Failed to activate the participant in the SML. Participant was persisted without SML activation.|
|GGW-361||Failed to activate participant in the SML.|
|GGW-362||Failed to inactivate participant in the SML|
|GGW-363||Failed to deactivate the participant in the SML. Participant was persisted without SML deactivation.|
|GGW-901||There seems to have been a problem when storing data to database, this error most likely needs manual attention from Tickstar Support.|
|GGW-902||Failed to delete an Endpoint record.|
|GGW-903||Failed to find location of SML management WS.|
|GGW-904||Failed to communicate with SML management service.|
|GGW-999||This error indicates that we were not able to understand or amend what went wrong. Please contact Tickstar Support with a copy of this message, timestamp and a detailed description of what you intended to do when this error occurred.|
- Learn more about PEPPOL in the Frequently Asked Questions section.