Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.
If you are upgrading to Subscribe Version 3.17.0 and calling the subscribe APIs externally, this migration is mandatory.
Welcome to the Subscribe API documentation! This guide is intended to assist developers, system administrators, and API integration stakeholders to understand, mitigate, and effectively adapt to the breaking changes in application programming interfaces (APIs). Breaking changes are modifications that can interrupt the normal functioning of dependent systems, causing compatibility issues.
This guide explains how to migrate from the older to the newer APIs that have been listed below.
This section outlines the process to be followed in order to migrate from the old Billing API endpoints to the new Payment API endpoints within the Payment, EZPay, Update EZPay Info, and Restart flows. Additionally, the "Create Payment Method" and "Get Payment Method By ID" endpoints of the Billing API have been refactored. This section also shows a comparison of the old and new APIs.
The endpoints covered in this section are as listed below:
This endpoint is used to create a payment method for a recurring payment (EZPay) in Circulation Systems (NCS Circ, CircPro, Saxo, and Matrix) and assign it to a subscription in Naviga System.
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
URL
/Billing/Payments/{subscriptionId}/EzPaySignup
/Payment/EzPay
Method
POST
POST
Input Example
NCS (DTI)
Saxo (DSI)
CircPro
Matrix
POST
/Payment/EzPay
This endpoint is used to create a payment method for a recurring payment (EZPay) in Circulation Systems and assign it to a subscription in Naviga System.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System.
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System.
DonationAmount
Decimal
Donation amount.
TipAmount
Decimal
Tip amount.
PaymentOptionAmount
Decimal
EZPay Option Amount that will be paid.
RenewalTerm
String
Indicates the term to the Circulation System Provider. Applicable only for Matrix, CircPro, and NCS.
RenewalLength
String
Indicates the length to the Circulation System Provider. Applicable only for Matrix, CircPro, and NCS.
This section outlines the process to be followed in order to migrate from the old UserAPI endpoints to the new UsersOrchestratorAPI endpoints. This section also shows a comparison of the old and new APIs.
The endpoints covered in this section are as listed below:
In order to redirect to UserAPI or to UsersOrchestratorAPI, ProxyAPI must have the following settings in place:
MG2 Control Internal setting, UsersOrchestrator - Its value includes a "string.Format" that must be utilized to determine the correct API route. The value by default is "{0}/UsersOrchestrator".
Note: Since the ProxyAPI directly calls the UsersOrchestratorAPI, GatewayAPI is not involved in the request chain.
IgnoreProvider Considerations
This flag is included in the Body or QueryString of certain endpoints.
This parameter is used to retrieve only SubscribeRegistration results while ignoring third-party integration services. This is an optional parameter that modifies the workflow execution.
The UserOrchestrator API also includes the registration status in the API response.
The GET /Users
and GET /Users/id
endpoints will include the output parameter, State, which returns the status of a registration.
The registration's status will be returned as follows:
If the tenant has been associated with a third-party authentication system such as Auth0, Firefly, etc., the State will be returned as Standard.
If the tenant has been associated with MG2 Auth:
When the Password field in the database remains blank, the State will be Lite.
When the Verified field in the database has been set to False, the State will be Unverified.
When the Password field hasn't been blank and the Verified field has been set to true, the State will be Standard.
The POST /Users
endpoint will display an error when trying to create a registration that already exists in the database and has the Verified field set to false.
The POST /Users/Authentication
endpoint will display an error when trying to login with an Unverified or Lite registration.
This endpoint is used to retrieve the payment method information from the Naviga System based on the provided input parameter, PaymentMethodId
.
Note: For the time being, both the old and new endpoints are in the Billing API.
URL
/Billing/{subscriptionId}/PaymentMethods/{paymentMethodId}
/Billing/PaymentMethods/{paymentMethodId}
Method
GET
GET
Input Example
FromUri, subscriptionId and paymentMethodId
/Billing/1/PaymentMethods/1
FromUri, paymentMethodId
/Billing/PaymentMethods/1
GET
/Billing/PaymentMethods/{paymentMethodId}
This endpoint is used to retrieve the payment method information from the Naviga System based on the provided input parameter, PaymentMethodId
.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System
This endpoint is used to perform a one-time payment in Circulation Systems (NCS Circ, CircPro, and Matrix).
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
URL
/Billing/Payments/{subscriptionId}/ApplyPayment
/Payment
Method
POST
POST
Input Example
POST
/Payment
This endpoint is used to perform a one-time payment in Circulation Systems.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System
DonationAmount
Decimal
Donation amount
TipAmount
Decimal
Tip amount
TotalAmount*
Decimal
The total amount being paid (PaymentOptionAmount + TipAmount + DonationAmount + ProcessingFeeAmount + ProcessingFeeTaxAmount).
If the PaymentType is Credit Card for NCS clients, an Activation Fee is charged to the TotalAmount.
Total Amount for NCS = PaymentOptionAmount + TipAmount + DonationAmount + ProcessingFeeAmount + ProcessingFeeTaxAmount + ActivationFee
PaymentOptionAmount*
Decimal
The Payment Option Amount being paid.
IgnoreFee
Boolean
Indicate whether the Activation Fee should be ignored. Applicable for NCS clients.
TransactionId
String
Transaction ID created by the Payment Gateway when creating a new Payment Method. Applicable for Matrix clients.
ProcessingFeeAmount
Decimal
The Fee amount being paid. Applicable for NCS clients.
ProcessingFeeTaxAmount
Decimal
The Fee tax amount being paid. Applicable for NCS clients.
This endpoint is used to update the payment method for a recurring payment (EZPay) in Circulation Systems (NCS Circ, CircPro, and Matrix) and assign it to a subscription in Naviga System
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
The new endpoint fires the CHGCC/CHGACH event and assigns the payment method to the subscription.
URL
/Billing/{subscriptionId}/PaymentMethods
/Payment/EzPay
Method
PUT
PUT
Input Example
PUT
/Payment/EzPay
This endpoint is used to update the payment method for a recurring payment (EZPay) in Circulation Systems and assign it to a subscription in Naviga System.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON web token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System.
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System.
This endpoint is used to create a new payment method for a Subscriber using either a Credit Card or a Bank Account and to create a new record in the PaymentMethod table in the database.
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
Note: For the time being, both the old and new endpoints are in the Billing API.
URL
/Billing/{subscriptionId}/PaymentMethods
/Billing/PaymentMethods
Method
POST
POST
Input Example
Credit Card example:
BankAccount example:
POST
/Billing/PaymentMethods
This endpoint is used to create a new payment method for a Subscriber using either a Credit Card or a Bank Account and to create a new record in the PaymentMethod table in the database.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System
BillingAddressId
Integer
Unique identifier of the current Subscriber Billing address in Naviga System.
BillingSystemPaymentMethodId
String
Unique identifier of the payment method in Naviga System.
(Used by the data team.)
HolderName*
String
For a Bank Account payment method, it’s the Subscriber’s name, and for a Credit Card payment method, it’s the Credit Card name.
CreditCard.CreditCardType
Integer
Represents the credit card type. Possible values: American Express (1), Visa (2), MasterCard (3), Diners (4), Discover (5).
CreditCard.CreditCardNumber
String
Masked Credit Card number.
Required if Payment Method is Credit Card.
CreditCard.CreditCardExpirationYear
Integer
Credit card expiration year.
Required if Payment Method is Credit Card.
CreditCard.CreditCardExpirationMonth
Integer
Credit card expiration month.
Required if Payment Method is Credit Card.
BankAccount.BankAccountNumber
String
Bank account number.
Required if Payment Method is Bank Account.
BankAccount.BankName
String
Name of the bank.
Required if Payment Method is Bank Account.
BankAccount.BankAccountType
Integer
Represents the bank account type.
Required if Payment Method is Bank Account.
Possible values: CheckingsAccount(1), SavingsAccount (2), CorporateCheckingsAccount(3).
PaymentMethodType
Integer
Represents the payment method type.
Possible values: CreditCard(1), BankAccount(2), MerchantAcceptedPayment(3), Coupon(4), PayPal(5), PayPalExpress(6), iTunes(7), GooglePlay(8), ApplePay(9), AmazonInApp(10), SubscribeWithGoogle(11), GooglePay(12), ExternalPayment(13), Piano(14)
PaymentGatewayCustomerId
String
Unique identifier of the Payment Method’s owner in the Payment Gateway Systems.
Required if Payment Method is Credit Card.
Note: This parameter is not managed by all payment gateways; however, Stripe, Braintree, and NavigaPay do.
PaymentGatewayToken
String
Unique identifier of the Payment Method in the Payment Gateway Systems (Payway, AuthorizeNET, Stripe, Braintree, NavigaPay, etc).
Required (and mandatory) if Payment Method is Credit Card.
PaymentMethod.CreditCard.CardOwner
String
Credit card Owner name.
Required if Payment Method is Credit Card.
BankAccount.BankRoutingNumber
String
Bank account routing number.
Required if Payment Method is Bank Account.
This endpoint is used to restart a stopped subscription in Circulation Systems (NCS Circ and Matrix).
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
URL
/Billing/Payments/{subscriptionId}/RestartPayment
/Payment/Restart
Method
POST
POST
Input Example
POST
/Payment/Restart
This endpoint is used to restart a stopped subscription in Circulation Systems (NCS Circ and Matrix)
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System
DonationAmount
Decimal
Donation amount
TipAmount
Decimal
Tip amount
TotalAmount*
Decimal
The total amount being paid (PaymentOptionAmount + TipAmount + DonationAmount + ProcessingFeeAmount + ProcessingFeeTaxAmount - Subscription’s Balance).
If the MG2 Control Setting "Restart.ApplyCreditBalance" has been turned off and the Subscription’s Balance is positive, then it won’t be deducted from the total. If Subscription’s Balance is negative (debt), it should always be in the math.
Take into consideration that each consumer application should do the math, so the setting should be consumed there too.
PaymentOptionAmount*
Decimal
The Restart Option Amount being paid.
TransactionId
String
Transaction ID created by the Payment Gateway when creating a new Payment Method. Applicable for Matrix clients.
ProcessingFeeAmount
Decimal
The Fee amount being paid. Applicable for NCS clients.
ProcessingFeeTaxAmount
Decimal
The Fee tax amount being paid. Applicable for NCS clients.
CreateRestartEvent
Boolean
Indicates whether to create the RESTART event.
For Saxo, CreateRestartEvent
can be set to False if the client chooses to restart payment without restarting the subscription. Otherwise, this is optional.
RenewalLength
String
Indicates the Circulation System Provider's renewal length. Applicable for CircPro and NCS.
RenewalTerm
String
Indicates the Circulation System Provider's renewal term. Applicable for CircPro and NCS.
RestartDate
DateTime
Indicates the Subscription’s Restart Date. Currently, this is applicable for CircPro and Matrix.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to retrieve the user's information based on the provided Query String parameters.
Based on the value of Flow.UserProvider and the IgnoreProvider input parameter, the API gives user information in the following way:
If no valid value is provided in Flow.UserProvider, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to True, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to False, the user's details are retrieved from both the integration service and the subscribe registration. The combined information is displayed in the response.
Note
MG2 control flow setting: Flow.UserProvider value should be set to "Auth0," "Gigya," "SSOR", or "Firefly", depending on the third-party system or integration service being used.
MG2 control flow setting, "Flow.Users.RedirectToOrchestrator", value has to be set to 1 for the ProxyAPI redirection to the UsersOrchestratorAPI instead of the UserAPI.
The following parameters have been deprecated.
Type
OnlyActive
SortBy
SortOrder
UsersPerPage
LookupInUserProvider
AuthSystemId
A set of new parameters has been added.
PageSize
OrderBy
OrderByType
IgnoreProvider
Note: The old model is in PascalCase, while the new model is in CamelCase.
URL
/User/{queryString}
/v4/Users/{queryString}
Method
GET
GET
Response
GET
/v4/Users/{queryString}
This endpoint is used to gets the user's information from both the integration service and the subscribe registration based on the provided Query String parameters.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
CustomerRegistrationId*
String
Unique identifier for the user in the authentication provider.
IgnoreProvider
Boolean
Indicates whether to retrieve the user details from the integration service.
EncryptedEmail
String
Encrypted email of the user
String
Email or partial email address of the user
PageSize
Integer
Maximum number of items returned per request.
Default value 10.
PageNumber
Integer
Requested page number of pagination. Default value 1.
OrderByType
Integer
Sort the records in ascending (0) or descending (1) order.
OrderBy
Integer
Sort the records based on the column number.
FirstName
String
User’s first name.
LastName
String
User’s last name.
Metadata
Dictionary <String, String>
Since it is a dictionary query parameter, each "Key-Value" pair must be sent individually with the prefix "metadata.".
For example, if the purpose is to filter users based on their first and last names, the query string will be: https://UrlBase/Users?metadata.firstName=FirstName&metadata.lastName=LastName”
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Error Code: UsersOrchestrator_E400 Error Message: Bad Request
Error Code: UsersOrchestrator_E400_02
Error Message: Invalid InputModel
Error Code: UsersOrchestrator_E500 Error Message: Internal Server Error
Error Code: UsersOrchestrator_E500_02
Error Message: There was a problem during the Get workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
-
SUBSCRIBE_USER_GET (4000)
New event created to get User from Subscribe
This endpoint is used to handle the one-time and recurring payment transactions to add tips.
Compared to the older model, the new input model requires just a few parameters, as explained in detail below.
URL
/Billing/Payments/{subscriptionId}/AddTip
/Payment/Tip
Method
POST
POST
Input Example
POST
/Payment
This endpoint is used to handle the one-time and recurring payment transactions to add tips.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-MediaGroupCode*
String
Media Group Code of the Tenant
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
SubscriptionId*
Integer
Unique identifier of the Subscription in Naviga System
PaymentMethodId*
Integer
Unique identifier of the payment method in Naviga System
TipAmount*
Decimal
Tip amount
ProcessingFeeAmount
Decimal
The Fee amount being paid. Applicable for NCS clients.
ProcessingFeeTaxAmount
Decimal
The Fee tax amount being paid. Applicable for NCS clients.
IsTipAutoRenew*
Boolean
Indicates whether the Tip amount should be auto-renewed.
TotalAmount*
Decimal
Total amount being paid (TipAmount + ProcessingFeeAmount + ProcessingFeeTaxAmount)
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API.
With the input parameter Customer Registration ID (CRID), the API gets the user's information from both the integration service and the subscribe registration. The response displays the combined information.
Based on the value of Flow.UserProvider and the IgnoreProvider input parameter, the API gives user information in the following way:
If no valid value is provided in Flow.UserProvider, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to True, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to False, the user's details are retrieved from both the integration service and the subscribe registration. The combined information is displayed in the response.
Note
MG2 control flow setting: Flow.UserProvider value should be set to "Auth0," "Gigya," "SSOR", or "Firefly", depending on the third-party system or integration service being used.
MG2 control flow setting, "Flow.Users.RedirectToOrchestrator", value has to be set to 1 for the ProxyAPI redirection to the UsersOrchestratorAPI instead of the UserAPI.
The parameter, Type, has been deprecated.
A new parameter, IgnoreProvider, has been added.
Note: The old model is in PascalCase, while the new model is in CamelCase.
GET
/v4/Users/{customerRegistrationId}/?ignoreProvider={boolean}
This endpoint is used to gets the user's information from both the integration service and the subscribe registration based on the CustomerRegistrationId.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Error Code: UsersOrchestrator_E400 Error Message: Bad Request
Error Code: UsersOrchestrator_E400_01
Error Message: Invalid Id
Error Code: UsersOrchestrator_E500 Error Message: Internal Server Error
Error Code: UsersOrchestrator_E500_01
Error Message: There was a problem during the GetById workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API.
With the input parameter Email (Subscriber’s email), the API gets the user's information from both the integration service and the subscribe registration. The response displays the combined information.
Based on the value of Flow.UserProvider and the IgnoreProvider input parameter, the API gives user information in the following way:
If no valid value is provided in Flow.UserProvider, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to True, the API retrieves user information from the Subscribe Registration API.
If a valid value is provided in Flow.UserProvider and the input parameter IgnoreProvider is set to False, the user's details are retrieved from both the integration service and the subscribe registration. The combined information is displayed in the response.
The parameter, Type, has been deprecated.
A new parameter, IgnoreProvider, has been added.
Note: The old model is in PascalCase, while the new model is in CamelCase.
GET
/v4/Users?email={email}&ignoreProvider={boolean}
This endpoint is used to gets the user's information from both the integration service and the subscribe registration based on the Email.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Error Code: UsersOrchestrator_E400_02 Error Message: Invalid InputModel
Error Code: UsersOrchestrator_E400 Error Message: Bad Request
Error Code: UsersOrchestrator_E500 Error Message: Internal Server Error
Error Code: UsersOrchestrator_E500_02
Error Message: There was a problem during the Get workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint retrieves the user's information from both the integration service and the subscribe registration based on the input parameter Encrypted Customer Registration ID.
With the input parameter Encrypted CRID, the API gets the user's information from both the integration service and the subscribe registration. The response displays the combined information.
Note: The old model is in PascalCase, while the new model is in CamelCase.
GET
/v4/Users?encryptedCustomerRegistrationId={encryptedCustomerRegistrationId}
This endpoint is used to gets the user's information from both the integration service and the subscribe registration based on the Encrypted Customer Registration ID.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Error Code: UsersOrchestrator_E400_02 Error Message: Invalid InputModel
Error Code: UsersOrchestrator_E400
Error Message: Bad Request
Error Code: UsersOrchestrator_E500 Error Message: Internal Server Error
Error Code: UsersOrchestrator_E500_02
Error Message: There was a problem during the Get workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API.
With the input parameter Encrypted Email (Subscriber’s encrypted email), the API gets the user's information from both the integration service and the subscribe registration. The response displays the combined information.
Note: The old model is in PascalCase, while the new model is in CamelCase.
GET
/v4/Users?email={email}&ignoreProvider={boolean}
This endpoint is used to gets the user's information from both the integration service and the subscribe registration based on the Encrypted Email.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Error Code: UsersOrchestrator_E400_02 Error Message: Invalid InputModel
Error Code: UsersOrchestrator_E400
Error Message: Bad Request
Error Code: UsersOrchestrator_E500 Error Message: Internal Server Error
Error Code: UsersOrchestrator_E500_02
Error Message: There was a problem during the Get workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to create a user.
When creating a passwordless user, UsersOrchestrator will generate a dummy password and the proper Change Password URL.
The old model is in PascalCase, while the new model is in CamelCase.
Cookie tokens will not be returned by the UsersOrchestrator API.
For custom fields, use Metadata.
POST
/v4/Users
This endpoint is used to create a user without a password.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to create a user.
The old model is in PascalCase, while the new model is in CamelCase.
Cookie tokens will not be returned by the UsersOrchestrator API.
For custom fields, use Metadata.
POST
/v4/Users
This endpoint is used to create a user.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to update a user based on the provided CustomerRegistrationId.
The old model is in PascalCase, while the new model is in CamelCase.
Cookie tokens will not be returned by the UsersOrchestrator API.
For custom fields, use Metadata.
PUT
/v4/Users/{customerRegistrationId}/
This endpoint is used to update a user.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
URL
/User/{type}?email={email}
/v4/Users?email={email}&ignoreProvider={boolean}
Method
GET
GET
Response
IgnoreProvider
Boolean
Indicates whether to retrieve the user details from the integration service.
Email*
String
Subscriber’s email.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
GETUSER (73)
AUTHSYSTEM_USER_GET (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
CREATELOGIN (68)
-
No user will be created but synchronized in our database
-
SUBSCRIBE_USER_UPDATE (4004)
New event to update User in Subscribe
-
SUBSCRIBE_USER_GET (4000)
New event to retrieve User from Subscribe
URL
/User/Encrypted/{Type}?encryptedCustomerRegistrationId={encryptedCustomerRegistrationId}
/v4/Users?encryptedCustomerRegistrationId={encryptedCustomerRegistrationId}
Method
GET
GET
Response
Encrypted Customer Registration ID*
String
Encrypted unique identifier for the user in authentication system.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
GETUSER (73)
AUTHSYSTEM_USER_GET (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
CREATELOGIN (68)
-
No user will be created but synchronized in our database
-
SUBSCRIBE_USER_UPDATE (4004)
New event to update User in Subscribe
-
SUBSCRIBE_USER_GET (4000)
New event to retrieve User from Subscribe
URL
/User/Encrypted?encryptedEmail={encryptedEmail}
/v4/Users?encryptedEmail={encryptedEmail}
Method
GET
GET
Response
Email*
String
Subscriber’s email.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
GETUSER (73)
AUTHSYSTEM_USER_GET (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
CREATELOGIN (68)
-
No user will be created but synchronized in our database
-
SUBSCRIBE_USER_UPDATE (4004)
New event to update User in Subscribe
-
SUBSCRIBE_USER_GET (4000)
New event to retrieve User from Subscribe
URL
/User/{customerRegistrationId}/{type}
/v4/Users/{customerRegistrationId}/?ignoreProvider={boolean}
Method
GET
GET
Response
CustomerRegistrationId*
String
Unique identifier for the user in the authentication provider.
IgnoreProvider
Boolean
Indicates whether to retrieve the user details from the integration service.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
CREATELOGIN (68)
-
No user will be created but synchronized in our database
GETUSERBYID (1042)
AUTHSYSTEM_USER_GETBYID (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
-
SUBSCRIBE_USER_GETBYID (4001)
New event created to get User By Id from Subscribe
-
SUBSCRIBE_USER_UPDATE (4004)
New event created to update User in Subscribe
URL
/User/Passwordless
/v4/Users
Method
POST
POST
Request
Response
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
String
Subscriber’s email.
CustomerRegistrationId
String
Unique identifier for the user in the authentication provider
EncryptedCustomerRegistrationid
String
Encrypted unique identifier for the user in authentication system.
VerifyEmail
Boolean
Default false.
If True is provided, then the registration will not be created right away. Naviga would wait until the user confirmed the registration by clicking the link in the verification email.
ReturnUrl
String
URL to which users must be redirected after they have successfully verified their registration.
FirstName
String
Subscriber’s first name.
LastName
String
Subscriber’s last name.
Metadata
Object
Metadata must be an object in camelCase format.
IgnoreProvider
Boolean
If the IgnoreProvider flag is false, it executes a Create operation through the ThirdParty system (Integration).
If the IgnoreProvider flag is true, it executes a Create operation through the SubscribeRegistration API (Subscribe).
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_07
The entered email address is still pending for verification.
400
UsersOrchestrator_E400_08
The email is already in use by another user.
400
UsersOrchestrator_E400_09
The metadata is invalid.
400
UsersOrchestrator_E400_17
Metadata Key or Value cannot contain more than 100 characters.
400
UsersOrchestrator_E400_23
The customer registration id already exists.
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
GETUSER (73)
AUTHSYSTEM_USER_GET (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
CREATELOGIN (68)
AUTHSYSTEM_USER_CREATE (4602)
SUBSCRIBE_USER_CREATE (4002)
For each CREATELOGIN old event, we now create two events. One is for the call to the third-party system, and the other is for the call to our database.
SUBSCRIBE_USER_CREATE is responsible for sending the email.
URL
/User
/v4/Users
Method
POST
POST
Request
Response
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
String
Subscriber’s email.
Metadata
Object
Metadata must be an object in camelCase format.
LastName
String
Subscriber’s last name.
FirstName
String
Subscriber’s first name.
IgnoreProvider
Boolean
If the IgnoreProvider flag is false, it executes a Create operation through the ThirdParty system (Integration).
If the IgnoreProvider flag is true, it executes a Create operation through the SubscribeRegistration API (Subscribe).
ReturnUrl
String
URL to which users must be redirected after they have successfully verified their registration.
VerifyEmail
Boolean
Default false.
If True is provided, then the registration will not be created right away. Naviga would wait until the user confirmed the registration by clicking the link in the verification email.
Password
String
Subscriber’s password.
EncryptedCustomerRegistrationid
String
Encrypted unique identifier for the user in authentication system.
CustomerRegistrationId
String
Unique identifier for the user in the authentication provider
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_07
The entered email address is still pending for verification.
400
UsersOrchestrator_E400_08
The email is already in use by another user.
400
UsersOrchestrator_E400_09
The metadata is invalid.
400
UsersOrchestrator_E400_17
Metadata Key or Value cannot contain more than 100 characters.
400
UsersOrchestrator_E400_23
The customer registration id already exists.
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
GETUSER (73)
AUTHSYSTEM_USER_GET (4601)
Renamed.
This event retrieves a User by Id from AuthSystem.
CREATELOGIN (68)
AUTHSYSTEM_USER_CREATE (4602)
SUBSCRIBE_USER_CREATE (4002)
For each CREATELOGIN old event, we now create two events. One is for the call to the third-party system, and the other is for the call to our database.
SUBSCRIBE_USER_CREATE is responsible for sending the email.
URL
/User/{customerRegistrationId}
/v4/Users/{customerRegistrationId}/
Method
PUT
PUT
Request
Response
CustomerRegistrationId*
String
Unique identifier for the user in the authentication provider
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Metadata
Object
Metadata must be an object in camelCase format.
LastName
String
Subscriber’s last name.
FirstName
String
Subscriber’s first name.
IgnoreProvider
Boolean
If the IgnoreProvider flag is false, it executes a Create operation through the ThirdParty system (Integration).
If the IgnoreProvider flag is true, it executes a Create operation through the SubscribeRegistration API (Subscribe).
Verified
Boolean
Indicates whether the user has confirmed the registration.
LastLogoutDate
DateTime
Subscriber’s last logout date in the Naviga platform.
RemoveLastLogoutDate
Boolean
Indicates whether to remove the Subscriber’s last logout date.
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_22
There was an error trying to update the user.
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
GETUSERBYID (1042)
AUTHSYSTEM_USER_GETBYID (4601)
SUBSCRIBE_USER_GETBYID (4001)
For each GETUSERBYID old event, we now create two events: one for the call to the third-party system and one for the call to our database.
UPDATEUSER (712)
AUTHSYSTEM_USER_CREATE (4602)
SUBSCRIBE_USER_CREATE (4002)
For each UPDATEUSER old event, we now create two events: one for the call to the third-party system and one for the call to our database.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to update the email of a user based on the provided CustomerRegistrationId.
Note: The old model is in PascalCase, while the new model is in CamelCase.
URL
/User/{customerRegistrationId}
/v4/Users/{CustomerRegistrationId}/Email
Method
PUT
PATCH
Request
Response
PATCH
/v4/Users/{CustomerRegistrationId}/Email
This endpoint is used to update the email of a user.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
CustomerRegistrationId*
String
Unique identifier for the user in the authentication provider
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Email*
String
Subscriber’s email.
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_08
The email is already in use by another user
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
GETUSERBYID (1042)
AUTHSYSTEM_USER_GETBYID (4601)
SUBSCRIBE_USER_GETBYID (4001)
For each GETUSERBYID old event, we now create two events: one for the call to the third-party system and one for the call to our database.
CHGEMAIL (21)
AUTHSYSTEM_USER_CHANGEEMAIL (4610)
SUBSCRIBE_USER_CHANGEEMAIL (4011)
For each CHGEMAIL old event, we now create two events: one event is for the call to the third-party system and the other is for the call to our database.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to verify the email of a user based on the provided Email and Verification Code.
The old model is in PascalCase, while the new model is in CamelCase.
The UsersOrchestrator API only returns CRID and EncryptedCRID and does not return cookie tokens.
URL
/User/VerifyEmail
/v4/Users/Verification
Method
POST
POST
Request
Response
POST
/v4/Users/Verification
This endpoint is used to verify the email of a user based on the provided Email and Verification Code.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Email*
String
Subscriber’s email.
VerificationCode*
String
Unique code for verification of the registration.
Status Code
Code
Message
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_14
The email is not registered.
400
UsersOrchestrator_E400_15
The verification code is invalid.
400
UsersOrchestrator_E400_16
Email is already verified.
500
UsersOrchestrator_E500
Internal Server Error
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
GETUSER (73)
SUBSCRIBE_USER_GET (4000)
Renamed. This event will get User from Subscribe
CREATELOGIN (68)
SUBSCRIBE_USER_CREATE (4002)
Renamed. This event will create User in Subscribe
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to update the password of a user based on the provided CustomerRegistrationId.
Note: The old model is in PascalCase, while the new model is in CamelCase.
URL
/User/{customerRegistrationId}
/v4/Users/{CustomerRegistrationId}/Password
Method
PUT
PATCH
Request
Response
PATCH
/Users/{{customerRegistrationId}}/Password
This endpoint is used to update the password of a user.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
CustomerRegistrationId*
String
Unique identifier for the user in the authentication provider
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Password*
String
Subscriber’s password.
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
GETUSERBYID (1042)
AUTHSYSTEM_USER_GETBYID (4601)
SUBSCRIBE_USER_GETBYID (4001)
For each GETUSERBYID old event, we now create two events: one for the call to the third-party system and one for the call to our database.
CHGPWD (22)
AUTHSYSTEM_USER_CHANGEPASSWORD (4609)
SUBSCRIBE_USER_CHANGEPASSWORD (4010)
For each CHGPWD old event, we now create two events: one for the call to the third-party system and one for the call to our database. SUBSCRIBE_USER_CHANGEPASSWORD is responsible for sending the email.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to authenticate a user.
The old model is in PascalCase, while the new model is in CamelCase.
Cookie tokens will not be returned by the UsersOrchestrator API.
For custom fields, use Metadata.
URL
/Authenticate
/AuthenticateByToken
/v4/Users/Authentication
Method
POST
POST
Request
Response
POST
/v4/Users/Authentication
This endpoint is used to authenticate a user.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Token
String
Access token generated in the consumer application
Password
String
Subscriber’s password.
LoginName
String
Subscriber’s login name.
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
500
UsersOrchestrator_E500
Internal Server Error
500
UsersOrchestrator_E500_01
There was a problem during the GetById workflow.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
LOGIN (60)
AUTHSYSTEM_USER_GETBYID (4601)
SUBSCRIBE_USER_LOGIN (4006)
SUBSCRIBE_USER_GOOGLELOGIN (4012)
For each old LOGIN event, we now create separate events according to the way authentication is handled.
-
SUBSCRIBE_USER_UPDATE (4004)
New event to update User in Subscribe.
GETUSERBYID (1042)
SUBSCRIBE_USER_GETBYID (4001)
AUTHSYSTEM_USER_LOGIN (4605)
For each GETUSERBYID old event, we now create two events: one for the call to the third-party system and one for the call to our database.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and the Subscribe Registration API to create the STARTFORGOTPASSWORD (PWDREQ) event and send an email with a link to the subscriber.
The old model is in PascalCase, while the new model is in CamelCase.
UsersOrchestrator API doesn’t return PasswordResetLinkSent.
URL
/ForgotPassword
/v4/Users/ForgotPassword
Method
POST
POST
Request
Response
POST
/v4/Users/ForgotPassword
This endpoint is used to create the STARTFORGOTPASSWORD (PWDREQ) event and send an email with a link to the subscriber.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
ReturnUrl
String
URL to which users must be redirected after they have successfully verified their registration.
LoginName*
String
Subscriber’s login name.
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
500
UsersOrchestrator_E500
Internal Server Error
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
PWDREQ (64)
SUBSCRIBE_USER_STARTFORGOTPASSWORD (4009)
The new event is used to Start forgot password in Subscribe
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and the Subscribe Registration API to validate whether the received EncryptedEventId is a valid event for the forgot password flow.
The old model is in PascalCase, while the new model is in CamelCase.
The UsersOrchestrator API returns the EventId associated with the user.
If the event is invalid, the UsersOrchestrator API returns an error.
URL
/ForgotPassword/Validity
/v4/Users/ForgotPassword/{{EncryptedEventId}}/Validity
Method
POST
GET
Request
Response
GET
/v4/Users/ForgotPassword/{{EncryptedEventId}}/Validity
This endpoint is used to validate whether the received EncryptedEventId is a valid event for the forgot password flow.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
EncryptedEventId*
String
Encrypted unique identifier of the event.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
500
UsersOrchestrator_E500
Internal Server Error
This endpoint receives the new password to set based on an event and triggers the UpdatePassword workflow.
The old model is in PascalCase, while the new model is in CamelCase.
If the flow fails, the UsersOrchestrator API returns an error.
URL
/ForgotPassword/ChangePassword
/v4/Users/ForgotPassword/{{EncryptedEventId}}
Method
POST
POST
Request
Response
POST
/v4/Users/ForgotPassword/{{EncryptedEventId}}
This endpoint receives the new password to set based on an event and triggers the UpdatePassword workflow.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
EncryptedEventId*
String
Encrypted unique identifier of the event.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Password*
String
Subscriber’s password.
Error Code: UsersOrchestrator_E400
Error Message: Bad Request
Error Code: UsersOrchestrator_E400_02
Error Message: Invalid InputModel
Error Code: UsersOrchestrator_E500
Error Message: Internal Server Error
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
CHGPWD (22)
AUTHSYSTEM_USER_CHANGEPASSWORD (4609)
SUBSCRIBE_USER_CHANGEPASSWORD (4010)
For each CHGPWD old event, we now create two events: one for the call to the third-party system and one for the call to our database.
This section outlines the process to be followed in order to migrate from the Entitlements endpoints to the new EntitlementsOrchestrator API endpoints. This section also shows a comparison of the old and new APIs.
The endpoints covered in this section are as listed below:
In order to redirect to EntitlementsOrchestratorAPI, ProxyAPI must have the following settings in place:
MG2 Control Internal setting, EntitlementsOrchestrator - Its value includes a "string.Format" that must be utilized to determine the correct API route. The value by default is "{0}/EntitlementsOrchestrator/".
Note: Since the ProxyAPI directly calls the EntitlementsOrchestratorAPI, GatewayAPI is not involved in the request chain.
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and Subscribe Registration API to send or resend a Verification Code by email so that users can click on the verification link provided in the email in order to start using their new registration.
The old model is in PascalCase, while the new model is in CamelCase.
The UsersOrchestrator API only returns CRID and EncryptedCRID and does not return cookie tokens.
POST
/v4/Users/VerificationCode
This endpoint is used to verify the email of a user based on the provided Email and Verification Code.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
This endpoint is used to create Digital Access for the User based on the provided EntitlementCode and CustomerRegistrationId and create an Access Log record in the database.
Note: The old model is in PascalCase, while the new model is in CamelCase.
POST
/v4/Access
This endpoint is used to create Digital Access for the User based on the provided EntitlementCode and CustomerRegistrationId and create an Access Log record in the database.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Note:– The parameters subscriptionId
and accessLevelCode
are available only from version 3.17.0.3 onwards.
This endpoint is used to return the current access level (Premium, Upgrade, Purchase) based on the provided EntitlementCode and CustomerRegistrationId.
Note:– The GET method creates an entry in the Access_log
table only from version 3.17.0.3 onwards.
Note: The old model is in PascalCase, while the new model is in CamelCase.
GET
/v4/Access?CustomerRegistrationId={string}&EntitlementCode={string}
This endpoint is used to return the current access level (Premium, Upgrade, Purchase) based on the provided EntitlementCode and CustomerRegistrationId.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
URL
/VerifyEmail/Resend
/v4/Users/VerificationCode
Method
POST
POST
Request
Response
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Email*
String
Subscriber’s email.
ReturnUrl
String
URL to which users must be redirected after they have successfully verified their registration.
Status Code
Code
Message
400
UsersOrchestrator_E400
Bad Request
400
UsersOrchestrator_E400_00
Invalid InputModel - {Message}
400
UsersOrchestrator_E400_14
The email is not registered.
400
UsersOrchestrator_E400_18
The entered email address does not have any pending (and not expired) verification.
500
UsersOrchestrator_E500
Internal Server Error
GETUSER (73)
SUBSCRIBE_USER_GET (4000)
Renamed. This event will get User from Subscribe
VERIFYCODE (670)
SUBSCRIBE_USER_CREATEPENDING (4003)
Changed event. The event will create User with pending status in Subscribe
URL
/DigitalAccess
/v4/Access
Method
POST
POST
Request
Response
Note:– The parameters subscriptionId
and accessLevelCode
are available only from version 3.17.0.3 onwards.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
EntitlementCode*
String
Unique identifier of the Entitlement in the SubCon database
CustomerRegistrationId*
String
Unique identifier of the Registration in the SubCon database.
Device*
String
Caller’s Device
ReturnUrl
String
URL to which users must be redirected after the access has been created.
FromUrl
String
URL to which users will be directed to create access.
400
EntitlementsOrchestrator_E400
Bad Request
400
EntitlementsOrchestrator_E400_01
Invalid InputModel
400
EntitlementsOrchestrator_E400_02
Entitlements not found
400
EntitlementsOrchestrator_E400_03
AccessLevelCode is Purchase
400
EntitlementsOrchestrator_E400_04
AccessLevelCode is Upgrade
400
EntitlementsOrchestrator_E400_05
AccessLevelCode is not Premium
500
EntitlementsOrchestrator_E500
Internal Server Error
500
EntitlementsOrchestrator_E500_01
TemporaryEntitlement doesn't exist.
500
EntitlementsOrchestrator_E500_02
EntitlementAccess doesn't exist.
500
EntitlementsOrchestrator_E500_03
Entitlement's eEdition Url was not found.
URL
/DigitalAccess
/v4/Access?CustomerRegistrationId={string}&EntitlementCode={string}
Method
POST
GET
RequestBody
Response
EntitlementCode*
String
Unique identifier of the Entitlement in the SubCon database
CustomerRegistrationId*
String
Unique identifier of the Registration in the SubCon database.
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
400
EntitlementsOrchestrator_E400
Bad Request
400
EntitlementsOrchestrator_E400_01
Invalid InputModel
400
EntitlementsOrchestrator_E400_02
Entitlements not found
500
EntitlementsOrchestrator_E500
Internal Server Error