User access API


Our web to print software allows user access control via API. Access is controlled per web-to-print catalog with GRANT and DENY calls.

Call format

An access control call can be made using HTTP POST from your server to your ZetaPrints web-to-print portal.


  • ApiKey – see API page in your ZetaPrints account (required)
  • UserID – a GUID generated by a remote system (required)
  • Hash – a hash value for user password and server IP (required)
  • CorporateID – catalog ID to grant access to (required)

Query string for GRANT: http://[domain name]/API.aspx?page=api-user-grant;ApiKey=[your API key]

Query string for DENY: http://[domain name]/API.aspx?page=api-user-deny;ApiKey=[your API key]

<input type=”hidden” name=”UserID” value=”[GUID]” />

<input type=”hidden” name=”Hash” value=”[32 character sequence]” />

<input type=”hidden” name=”CorporateID” value=”[GUID]” />


  • <error /> – a missing or invalid parameter
  • <ok /> – the user no longer has access (even if it’s a repeat call the user already had no access)


<input type=”hidden” name=”UserID” value=”9A54D348-CC92-47ED-840E-2A22CF395D18″ />

<input type=”hidden” name=”Hash” value=”855c578152d2436dde27cbfe414c5cf3” />

<input type=”hidden” name=”CorporateID” value=”A85C9EFD-803C-494f-A5BD-2E1F3AFF5977″ />


UserID must exist with the same password in your database and in ZetaPrints web-to-print databse for the hash to be computed correctly. This is required to prove user ownership.

CorporateID must be an existing catalogue ID belonging to your account in ZetaPrints web-to-print system.

Grant and Deny calls are identical except for page parameter.

See also: