POST | /signup/api/formbuilder/model |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
TemplateId | body | int | No | |
BhUserID | body | string | No | |
UserType | body | string | No | |
ClientDocNo | body | string | No | |
FormType | body | string | No | |
ConfirmationNumber | body | int | No | |
NameValues | body | List<FormBuilderModelNameValue> | No | |
GroupPlans | body | string | No | |
makeFormSubmitRequest | body | bool | No | |
natId | body | int | No | |
chapId | body | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Name | form | string | No | |
Value | form | Object | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
message | form | string | No | |
modelStateId | form | int | 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/formbuilder/model HTTP/1.1
Host: devapi.billhighway.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"TemplateId":0,"BhUserID":"String","UserType":"String","ClientDocNo":"String","FormType":"String","ConfirmationNumber":0,"NameValues":[{"Name":"String","Value":{}}],"GroupPlans":"String","makeFormSubmitRequest":false,"natId":0,"chapId":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"message":"String","modelStateId":0}