practice.expandtesting.com APIpractice.expandtesting.com ↗
Submit and validate forms on Practice Expand Testing via API. Returns confirmed contact_name, phone, email, and message fields from the server.
curl -X POST 'https://api.parse.bot/scraper/57738870-8da1-4df2-9daa-4a85ee858fb5/submit_form' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "[email protected]",
"phone": "012-3456789",
"message": "Hello, this is a test",
"contact_name": "John Doe"
}'Typed Python client. Install the CLI, sign in, then pull this API’s generated client:
pip install parse-sdk parse login parse add --marketplace practice-expandtesting-com-api
parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: FormValidator SDK — submit a contact form and read the response."""
from parse_apis.Practice_Form_Validation_API import FormValidator, NotFoundError
client = FormValidator()
# Submit the form with contact details and a message.
try:
submission = client.form_submissions.submit(
contact_name="Jane Smith",
phone="012-3456789",
email="[email protected]",
message="Hello, I would like more information",
)
print(submission.message, submission.contact_name, submission.email)
except NotFoundError as exc:
print(f"Submission failed: {exc}")
print("exercised: form_submissions.submit")
Submits the form validation form with contact_name, phone, email, and message fields. The form posts to the confirmation endpoint and returns a response message indicating successful submission. All four fields are required for submission.
| Param | Type | Description |
|---|---|---|
| emailrequired | string | The email address to submit in the form. |
| phonerequired | string | The phone number to submit in the form (e.g. 012-3456789). |
| messagerequired | string | The message to submit in the form. |
| contact_namerequired | string | The contact name to submit in the form. |
{
"type": "object",
"fields": {
"email": "string - submitted email",
"phone": "string - submitted phone number",
"message": "string - confirmation message from the server",
"contact_name": "string - submitted contact name",
"message_sent": "string - submitted message"
},
"sample": {
"data": {
"email": "[email protected]",
"phone": "555-1234567",
"message": "Thank you for validating your ticket",
"contact_name": "Jane Smith",
"message_sent": "Hello, this is a test message"
},
"status": "success"
}
}About the practice.expandtesting.com API
The Practice Expand Testing Form Validation API exposes 1 endpoint — submit_form — that posts a contact form with four required fields and returns 5 structured response fields confirming what the server accepted. It lets developers verify form submission behavior, test validation rules, and capture the server-side confirmation response including the echoed input values and a server-generated confirmation message.
What the API Covers
This API targets the form validation page at practice.expandtesting.com. The single submit_form endpoint accepts a POST request with four required fields: contact_name, phone, email, and message. All four must be present for the submission to succeed — omitting any one will not produce a valid confirmation response.
Response Fields
A successful call to submit_form returns five fields: contact_name and email echo back the values you submitted, phone returns the submitted phone number (expected format: 012-3456789), message_sent echoes the body of your message, and message carries the server-generated confirmation string indicating the form was accepted. These fields together let you assert both that input was received intact and that the server acknowledged the submission.
Intended Use
The source site is an open practice environment designed for testing web automation and form interaction. The API is well-suited for integration testing pipelines, QA tooling, and teaching scenarios where you need a real HTTP round-trip with a form submission and a predictable confirmation payload — without managing a test server yourself.
The practice.expandtesting.com API is a managed, monitored endpoint for practice.expandtesting.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when practice.expandtesting.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official practice.expandtesting.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Verifying that all four required form fields (contact_name, phone, email, message) are accepted correctly in an integration test
- Asserting that the server echoes back submitted values unchanged via the contact_name, email, phone, and message_sent response fields
- Validating phone number format (e.g. 012-3456789) against the server's acceptance criteria
- Checking that the server-generated confirmation message field returns the expected success string in automated test suites
- Teaching form submission and response parsing workflows using a live, stable practice endpoint
- Smoke-testing HTTP POST pipelines by confirming end-to-end round-trip behavior without setting up a dedicated test server
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does practice.expandtesting.com have an official developer API?+
What exactly does the submit_form endpoint return on a successful call?+
contact_name, email, and phone echo the values you submitted; message_sent echoes the message body you posted; and message contains the server's confirmation string indicating the form was accepted. There is no session token, submission ID, or timestamp in the response.