1. Home
  2. Documentation
  3. FAQ
  4. Getting Started

Getting Started

Step 1: Creating a Test Account

  • Where do I sign up for a test account?
    • Fill out this form using a valid e-mail address to create your test account.
  • Why do I need a test account for the Tripletex API?
    • A test account allows you to explore and test Tripletex API functionalities in a controlled environment without affecting your production data or requiring production credentials.
  • Can I use my test account credentials in the production environment?
    • No, credentials for the test environment are not valid in the production environment; both environments are separate and require their specific credentials.
  • How long is the test account active, and can it be extended?
    • By default, the test account is active for six months. You can contact us to request renewed trial period if needed.
  • What should I do if I lose my test account tokens?
    • Unfortunately, we cannot recover lost tokens or application names, so be sure to save them securely upon creation. A new test account can be created for new credentials.
  • What is the process to create a test account?
    • You need to fill out a form with your contact details, verify your email, and set a password. Once done, you’ll immediately get access to our test environment.
  • Can I get a test account for the production environment?
    • Yes, if you have a commercial integration and your integration is approved for production. Then you can request a test account in production.

Step 2: Explore

  • How can I explore the functionalities of Tripletex?
    • You can explore by using the GUI to understand how things look and feel, and by using our interactive documentation to test endpoints directly in your web browser.
  • What’s the benefit of using the OpenAPI documentation for testing?
    • The OpenAPI, “Swagger”, documentation allows you to interactively test API endpoints, which is beneficial for troubleshooting and ensuring the functionality of your integration before deploying it fully.
  • How do I authenticate using our interactive documentation?
    • First use your consumer and employee tokens to create a session token via /token/session/:create.
      When authenticating using the padlock icon, use “0” (zero) as your username and your session token as the password. More on this here.
  • What is the difference between test and production instances?
    • The test instance (api-test.tripletex.tech) is for development and trial purposes, while the production instance (tripletex.no) is for live operations. Credentials are not interchangeable between these two environments.
  • Can I perform operations directly using the OpenAPI documentation before writing code?
    • Yes, testing operations in the interactive using the OpenAPI documentation can help you pinpoint issues more efficiently and validate that your requests work as intended before developing your integration’s code.
  • What should I do if I encounter an issue with the API?
    • First, reproduce the issue using our using the OpenAPI documentation to determine if it’s related to your code or not. This will help you provide us more detailed information when contacting support.

Step 3: Getting ready for production

  • How do I start integrating with Tripletex?
    • Begin by exploring our API documentation to understand the capabilities and setting up your integration in our test environment. This helps ensure everything functions as expected before moving to production.
  • What are the steps to gain access to the production environment?
    • It depends on what you’re building:
      • If you’re building an internal integration for your own company or group, there’s no need to wait. See how to generate a JWT token and authenticate.
      • If you’re building a commercial or multi tenant integration, offered to multiple customers or used between several clients, you need to apply for a consumer token. After testing in the test environment, submit your application via this form.
  • How long does it take to get approved for commercial production access?
    • The approval process typically takes 2-3 weeks, and this duration is standard for all applicants.
  • Can I expedite my production access application?
    • If you’re building a single-company integration, there’s no waiting — you can generate a token and get started immediately. For commercial and internal multi tenant integrations, no expedited process exists. All applications are evaluated equally.
  • What should I do if I don’t receive a response within the estimated time for production access approval?
    • If no response is given after the estimated time, please contact us using the details provided during your application to inquire about the status.
  • How can my integration be featured on the Tripletex integration marketplace?
    • A commercial integration with approved production access may apply to be published in the integration marketplace in-app. Read more about the marketplace here.

      This is a separate listing from the public integration overview. Integrators receive a form to apply for that in their approval email.
  • What options do end users have when setting up an employee token manually?
    • Users can choose from “All entitlements”, copy the user’s current entitlements, or assign them manually when generating an employee token with your application name. Entitlements may be changed later on.
  • Do I need to apply if I’m only integrating with my own Tripletex account?
    • No. If you’re connecting a single Tripletex account to another system — whether for your own company or a specific customer — you can generate an API token directly inside Tripletex. No application or approval is needed. The application process is only required for commercial integrations intended for multiple customers.
  • Can I start with a single-company integration and go commercial later?
    • Yes. For legitimate cases where an in-house integration grows into a product. When you decide to offer the integration to other customers, apply for a consumer token via this form. Until that application is approved, the integration must remain limited to the single Tripletex account it was built for. Using a JWT token to serve additional customers ahead of approval is not permitted.

How can we help?