Subpaas session key

API call to create a subpaas session.

API actions

API base path: panel/subpaas/session.

---

required permissions: subpaas: "create".

The returned hash grants access to the sub-dealer's panel. Treat it as a credential and handle it exactly as you would a hash from authentication.

Create sub-dealer session

post

/panel/subpaas/session/create

Open a panel session as one of your sub-dealers and return its session hash.

Use the returned hash exactly as one returned by the authenticate operation. It grants access to that sub-dealer's panel, so treat it as a credential.

Authorizations

AuthorizationstringRequired

Enter the panel session hash with the "NVX " prefix, e.g. "NVX fa7bf873fab9333144e171372a321b06". Obtain the hash from the accountAuth operation.

Body

subpaas_idintegerRequired

Sub-dealer ID.

Example: 97834

Responses

200

Session opened as the sub-dealer

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

hashstringRead-onlyOptional

Session key for the sub-dealer's panel. Pass it in the Authorization header as NVX <hash>.

Example: fa7bf873fab9333144e171372a321b06

400

Bad request. The response body carries the API-level error code in status.code. Validation failures also include an errors array.

application/json

403

Operation not permitted, error code 13: the session lacks the required permission, or the dealer is not eligible to have sub-dealers.

application/json

default

Error response object

application/json

post/panel/subpaas/session/create

POST /v2/panel/subpaas/session/create HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 20

{
  "subpaas_id": 97834
}

{
  "success": true,
  "hash": "fa7bf873fab9333144e171372a321b06"
}

Errors

• 13 –

  • The dealer is not PaaS type.

  • The dealer has a status other than NOT_BLOCKED.

  • The dealer's tariff does not allow SubPaaS accounts.

  • The found SubPaaS is not in NOT_BLOCKED status.