Newuserpack

From SafeStamper API documentation
Jump to navigation Jump to search

This operation activates a professional or corporate account for the user and links it to the authorization, so it will be removed if the authorization is deleted.

URL

https://www.safestamper.com/api/newuserpack

Parameters

  • sharedkey: Your API client shared key
  • authkey: Authkey to enable subscription services
  • accounttype: Account type that will be enabled to the user (professional|corporate|premium). Deprecated (in future version all userpacks are premium and this field will be removed)
  • usercount: Number of users can be use this subscription. Min value: 1. Required for premium accounttype
  • extranavigations: Number of extra navigations to add to this subscription. Min value: 0. Optional for premium accounttype
  • extrasigneddocuments: Number of extra signed document credits to add to this subscription. Min value: 0. Optional for premium accounttype
  • timestamppacks: Number of daily timestamp packs to add to this subscription. Min value: 0. Optional for premium accounttype
  • authcodes: Indicate if authorization codes are enabled for this subscription. Values: true/false. Optional for premium accounttype
  • unlimitedsenders: Indicate if alternative sender e-mails are enabled for this subscription. Values: true/false. Optional for premium accounttype
  • signature: Parameters signature, as explained in Signature parameter

Returns

HTTP 200 OK

HTTP Errors

  • 400 Bad Request: the accounttype is not valid
  • 401 Unauthorized: authkey is not valid
  • 403 Forbidden:
    • Sharedkey or signature is not valid
    • API client is not a partner
  • 431 The user already has a professional or corporate account

Example

REQUEST:

https://www.safestamper.com/api/newuserpack
?accounttype=premium&authcodes=true&authkey=8639e12a-810c-4c51-8a62-c1b0fcf58bfd
&extranavigations=5&sharedkey=2w32i03wypba9l7ajyv8ukr23&signature=9ed808c15841a163836f6b2bccc47f6efb960ce9
&timestamppacks=0&unlimitedsenders=false&usercount=3

RESPONSE:

HTTP 200 OK