POST | /signup/api/nat/{natID}/group/{groupID}/{userType}/user/{userID}/form/access/link |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
NatID | path | int | No | |
GroupID | path | int | No | |
UserID | path | int | No | |
UserType | path | string | No | |
AdminID | body | int | No | |
SubscriptionInvoiceID | body | long | No | |
SubscriptionLineageID | body | long | No | |
ClientSubscriberId | body | string | No | |
MemberSubscriptionInvId | body | int | No | |
IsPrintView | body | bool | No | |
IsBillMeLaterSubscription | body | bool | No | |
RenewedMemberSubscriptionInvID | body | long | No | |
IsRenewal | body | bool | No | |
ClientSubscriptionTypeID | body | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Rel | form | string | No | |
Uri | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /signup/api/nat/{natID}/group/{groupID}/{userType}/user/{userID}/form/access/link HTTP/1.1
Host: devapi.billhighway.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"NatID":0,"GroupID":0,"UserID":0,"UserType":"String","AdminID":0,"SubscriptionInvoiceID":0,"SubscriptionLineageID":0,"ClientSubscriberId":"String","MemberSubscriptionInvId":0,"IsPrintView":false,"IsBillMeLaterSubscription":false,"RenewedMemberSubscriptionInvID":0,"IsRenewal":false,"ClientSubscriptionTypeID":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Rel":"String","Uri":"String"}