Support – Seequent Developers

How do I become a Seequent Technology Partner / How do I get access to the Seequent Developer Portal?

Seequent’s current APIs are available to explore here in the Seequent Developer Portal. New APIs are being developed and released every release. In order to use the APIs, you will require a token which is assigned to Technology Partners or approved Seequent Customers who have met a specific set of criteria. If you wish to become a Technology partner, please send us a request via the form here.

How do I get an authentication token?

API Authorisation Tokens are provided to approved partners by our Product Management team. These are sent via secure transfer. We are always excited to work with new partners in order to expand the Seequent Evo ecosystem, so get in touch today to join our partner program.

Can I have a proprietary service?

No. Seequent is fostering the Seequent Evo environment to be inclusive and open to all parties wanting to interact with Seequent technologies, products, services and customers.

Where can I find the terms and conditions my organisation needs to accept in order to use Seequent Evo APIs?

The standard terms and conditions for Seequent users, products, services, APIs and online services can be found here. You will also need to accept the sandbox terms and conditions before you will be granted access to the developer environment. For software vendors looking to integrate, your Partner Manager will provide you with the current terms if your partnership progresses. For Seequent customers, talk to your account manager for more information about how you can gain access to the developer sandbox.

What are the service charges for accessing the Seequent Evo APIs?

There may be some costs associated with using services and APIs in the future, particularly when this involves data usage, storage or high volume computing. Our aim is to be transparent and open about these costs if/when they are introduced.

How do I obtain a secure client certificate for my organisation?

Your organisation almost certainly already has one. What is required is a Domain Validated (DV) SSL certificate, the same as used to enable the use of HTTPS on a website. It must be issued by a Certificate Authority (CA), be 2048 bits in strength, with a 1-year expiry. This is typical for a certificate obtained for your organisation’s website. However, if you are wishing to use a new domain for the purposes of developing your Seequent Evo integrated product or service, you will need to obtain a suitable DV certificate for the new domain from a CA. Please provide the certificate fingerprint to Seequent to be registered and whitelisted for API access.

Can I use a self-signed SSL certificate?

No. The DV Certificate needs to be issued by a Certificate Authority (CA). While there are Certificate Authorities offering premium services and charging for these, it should also be possible to use DV Certificates from a CA that provides a free service.

What is the purpose of the JSON Web Token?

Seequent Evo APIs use JSON Web Tokens (JWTs) to contain the access claims a partner is authorised to make for access to a customer’s data set. The signed JWT verifies that the claims have been transmitted without modification.

What is mTLS and why is it being used by Seequent for the APIs?

Mutual TLS is a method of mutual authentication. It verifies that the parties at each end of a network connection are who they claim to be by verifying their private key. Mutual TLS allows us to make use of a zero-trust security model that helps Seequent to keep its APIs secure. It also ensures our clients data is kept secure.

Our organisation is a customer of Seequent products, not a third-party product/service provider. Can we use Seequent’s APIs or is it only for integration partners?

You can certainly use Seequent APIs. The Seequent Evo ecosystem is designed to cater for the interactions between Seequent, a Seequent customer, and a third-party partner. This system is also fully capable of permitting a Seequent customer to develop in-house tools to interact directly with Seequent products and services, without the involvement of a third-party partner.

Will other organisations partnering with Seequent be able to see the data and activities of our development team in the sandbox environment?

Absolutely not. Each partner will be given their own copy of a fictional organisation’s Seequent Central instance to interact with in the sandbox environment. Because each partner needs administrative access to that fictional customer Seequent Central instance, it is not feasible for all the partners to share an instance. Your development team can work on their project with the assurance that no other partner has a way of seeing your development activities in the sandbox.

What file types can be stored in the Data service?

The File API accepts and stores any geoscience file type and other file types commonly used by Seequent and other geoscience software.

Can I modify the file I have already stored?

The initial version of the File API does not provide for a “modify” command. However, when using the PUT Upload A File endpoint to save a file of the same name as an existing file, a new version of the file will be created.

Can I read the file back out of the data store once it has been stored? Can I delete it?

The initial version of the File API does not provide for “read” or “delete” commands, because this initial deployment of an endpoint service is intended to get all the essential pieces in place to enable future endpoint deployments. Those with access permissions will be able to access the file from within Seequent Central.

Does Seequent have a Postman workspace?

Anyone can access and use the Seequent Evo workspace in Postman here. This space enables you to create tokens and links in order to interact with our APIs.

We’re here to help