Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This documentation is intended to be the basis for ERP/CRM integration projects into Secure Service symmedia Hub (SSH). The SSH symmedia Hub offers a standard graphQL interface that can be used to integrate third party systems.

...

To identify objects like customers, machines, service cases… in both systems (SSH symmedia Hub and SAP), the SSH symmedia Hub provides an external ID field for each object. This can be filled with corresponding unique identifiers from the SAP- / ERP system.

Authentication

All Secure Service symmedia Hub API queries and mutations require dual authentication using a valid API Key and a valid token. You need to include both in the HTTP headers of your requests.

...

To authenticate applications programmatically (without the need for 2FA) we are using the OAuth 2.0 Client Credentials Flow. The application and our authorization server need to share a secret/certificate, which will be generated by the SSH symmedia Hub platform when adding a new application in the portal.

...

Since service organizations in SSH symmedia Hub are associated with permissions, it is recommended to create them manually.
As of today, this object is missing the External ID. However, it will be added by symmedia if required.

...

Info
titleImportant Remark

This manual is based on the first version of the Secure Service symmedia Hub Public API. Even so we do our best to keep the API free of breaking changes, they might occur in the future. Breaking changes will be announced upfront and there will always we a transition time of at least 6 months.

...