Verify in depth

Every control and text this screen shows, in screen order. The list is read from the demo by a crawl, and CI fails when the screen changes without its entry here.

SMS > Verify shows every one-time code your app requested through the Twilio Verify API, and lets you force any outcome.

The screen as a whole: Verify.

The numbers match the entries below. The picture shows the first screenful; controls further down, and texts, have no marker.

On the screenCopy Anchor Link

1. VerifyCopy Anchor Link

Heading.

• What it does: Names the screen, in the header and above the tabs.

2. Read the Verify guideCopy Anchor Link

Link.

• What it does: Opens this screen's page in the user guide, in a new tab.
• Links to: Verify.

3. Twilio Verify emulation: every code your app requests, its attempts and expiry, and controls to force any outcome.Copy Anchor Link

Text.

• What it does: Explains the screen.

4. VerificationsCopy Anchor Link

Tab.

• What it does: Every verification your app started, newest first.
• Same action elsewhere: REST GET /api/v1/verify, CLI sendmock verify list, MCP sendmock_verify_list

5. ServicesCopy Anchor Link

Tab.

• What it does: The Verify services apps start verifications against.
• Same action elsewhere: REST GET /api/v1/verify/services, CLI sendmock verify services list, MCP sendmock_verify_service_list

6. AllCopy Anchor Link

Button.

• What it does: Shows every verification.

7. PendingCopy Anchor Link

Button.

• What it does: Shows only verifications still waiting for a correct code.

8. ApprovedCopy Anchor Link

Button.

• What it does: Shows only approved verifications.

9. FailedCopy Anchor Link

Button.

• What it does: Shows only verifications that expired, were cancelled or ran out of attempts.

10. Search verificationsCopy Anchor Link

Field.

• What it does: Filters by phone number, email address or service.

11. ToCopy Anchor Link

Column.

• What it does: Who the code went to.

12. ChannelCopy Anchor Link

Column.

• What it does: SMS, WhatsApp, email or call.

13. ServiceCopy Anchor Link

Column.

• What it does: The Verify service it belongs to.

14. CodeCopy Anchor Link

Column.

• What it does: The code that was sent.

15. StatusCopy Anchor Link

Column.

• What it does: Pending, approved, canceled, expired or max attempts reached.

16. AttemptsCopy Anchor Link

Column.

• What it does: How many checks were made, against the service's limit.

17. TimeCopy Anchor Link

Column.

• What it does: When it was started.

18. …Copy Anchor Link

Link, in each row.

• What it does: Opens the verification's details.
• Same action elsewhere: REST GET /api/v1/verify/{verificationSid}, CLI sendmock verify show, MCP sendmock_verify_get

19. Copy codeCopy Anchor Link

Button, in each row.

• What it does: Copies the code, to type it into your app.

A verification is openCopy Anchor Link

20. VerificationCopy Anchor Link

Heading.

• What it does: The details drawer of one verification.

21. Code, attempts and everything that happened to it.Copy Anchor Link

Text.

• What it does: Explains the drawer: the code, each check with its result, and the timeline.

22. Copy codeCopy Anchor Link

Button.

• What it does: Copies the code.

23. Open the messageCopy Anchor Link

Link.

• What it does: Opens the SMS or email the code was delivered in.
• Links to: SMS.

24. Force a stateCopy Anchor Link

Heading.

• What it does: Moves the verification to a final state by hand, to test what your app does then.

25. ApproveCopy Anchor Link

Button.

• What it does: Approves the verification, as a correct code would.
• What it changes: Fires verify.checked with the status approved.
• Same action elsewhere: REST POST /api/v1/verify/{verificationSid}/force, CLI sendmock verify force, MCP sendmock_verify_force

26. CancelCopy Anchor Link

Button.

• What it does: In the drawer, cancels the verification (fires verify.checked with the status canceled); in a dialog, closes it without saving.
• Same action elsewhere: REST POST /api/v1/verify/{verificationSid}/force, CLI sendmock verify force, MCP sendmock_verify_force

27. ExpireCopy Anchor Link

Button.

• What it does: Expires the verification, as when its time runs out.
• What it changes: Fires verify.expired.
• Same action elsewhere: REST POST /api/v1/verify/{verificationSid}/force, CLI sendmock verify force, MCP sendmock_verify_force

28. Max attemptsCopy Anchor Link

Button.

• What it does: Ends the verification as if too many wrong codes were tried; checks then get Twilio's 60202 error.
• What it changes: Fires verify.checked with the status max_attempts_reached.
• Same action elsewhere: REST POST /api/v1/verify/{verificationSid}/force, CLI sendmock verify force, MCP sendmock_verify_force

29. Your app sees the new state on its next check or fetch.Copy Anchor Link

Text.

• What it does: Explains when the forced state takes effect.

30. CloseCopy Anchor Link

Button.

• What it does: Closes the drawer or dialog.

Services tabCopy Anchor Link

31. Code length, an optional fixed code and how long codes stay valid.Copy Anchor Link

Text.

• What it does: Explains what a service sets.

32. New serviceCopy Anchor Link

Button.

• What it does: Opens the New Verify service dialog.

33. NameCopy Anchor Link

Column.

• What it does: The service's friendly name.

34. SIDCopy Anchor Link

Column.

• What it does: Its VA... SID, which apps put in the Verify API path.

35. Expires afterCopy Anchor Link

Column.

• What it does: How long a code stays valid.

36. ActionsCopy Anchor Link

Column.

• What it does: Edit and Delete for each service.

37. Copy SID of Acme …Copy Anchor Link

Button, in each row.

• What it does: Copies the service's SID, for your app's Verify calls.

38. Edit Acme …Copy Anchor Link

Button, in each row.

• What it does: Opens the service's settings: name, code length, expiry and fixed code.
• Same action elsewhere: REST PATCH /api/v1/verify/services/{serviceSid}, CLI sendmock verify services update, MCP sendmock_verify_service_update

39. Delete Acme …Copy Anchor Link

Button, in each row.

• What it does: Deletes the service after you confirm.
• Same action elsewhere: REST DELETE /api/v1/verify/services/{serviceSid}, CLI sendmock verify services delete, MCP sendmock_verify_service_delete

New Verify service dialogCopy Anchor Link

40. New Verify serviceCopy Anchor Link

Heading.

• What it does: The New Verify service dialog.

41. Apps start verifications against a service by its SID.Copy Anchor Link

Text.

• What it does: Explains the SID.

42. NameCopy Anchor Link

Field.

• What it does: The service's friendly name.

43. Code lengthCopy Anchor Link

Drop-down.

• What it does: How many digits the codes have, 4 to 10.

44. Expires after (minutes)Copy Anchor Link

Number field.

• What it does: How long a code stays valid.

45. Fixed code (optional)Copy Anchor Link

Field.

• What it does: A code every verification of this service uses, instead of a random one.

46. Leave empty for a random code. A fixed code makes tests deterministic.Copy Anchor Link

Text.

• What it does: Explains the fixed code.

47. CancelCopy Anchor Link

Button.

• What it does: In the drawer, cancels the verification (fires verify.checked with the status canceled); in a dialog, closes it without saving.
• Same action elsewhere: REST POST /api/v1/verify/{verificationSid}/force, CLI sendmock verify force, MCP sendmock_verify_force

48. Create serviceCopy Anchor Link

Button.

• What it does: Creates the service with a new SID.
• Same action elsewhere: REST POST /api/v1/verify/services, CLI sendmock verify services create, MCP sendmock_verify_service_create

49. CloseCopy Anchor Link

Button.

• What it does: Closes the drawer or dialog.

With no data yetCopy Anchor Link

50. No verifications yetCopy Anchor Link

Text.

• What it does: Shown when no verification was started yet.

51. Start one from your app with the Twilio Verify API. The code shows up here and in the SMS screen.Copy Anchor Link

Text.

• What it does: Explains how verifications arrive.

52. This machineCopy Anchor Link

Choice.

• What it does: Shows the addresses for an app on the same machine.
• What it changes: Shared with Settings > Connection and remembered in the browser.
• Same action elsewhere: REST GET /api/v1/info, CLI sendmock status, MCP sendmock_status

53. Docker hostCopy Anchor Link

Choice.

• What it does: Shows the addresses for an app in a container reaching SendMock on the host.

54. ComposeCopy Anchor Link

Choice.

• What it does: Shows the addresses for an app in the same Docker Compose project.

55. Copy Twilio base URLCopy Anchor Link

Button.

• What it does: Copies the base URL to give Twilio's SDK.

56. Copy Start a verificationCopy Anchor Link

Button.

• What it does: Copies the Verify API URL that starts a verification.

57. More snippetsCopy Anchor Link

Link.

• What it does: Opens Settings > Connection.
• Links to: Settings.

58. Start a sample verificationCopy Anchor Link

Button.

• What it does: Starts a verification against the first service and delivers its code by SMS.
• What it changes: Fires verify.started and stores the SMS with the code.
• Same action elsewhere: REST POST /api/v1/samples/{kind}, CLI sendmock sample, MCP sendmock_sample_send

59. Choose webhooks for Start a sample verificationCopy Anchor Link

Button.

• What it does: Opens Choose webhooks for this one action. Choose webhooks lists every enabled endpoint with a search box, the endpoints your rules would pick already checked, each checked one with Payload to see and edit its request, and says how many are chosen (or that no webhook will be sent). Its confirm button, named after the action, runs it once and sends the event to exactly the checked endpoints; Cancel runs nothing.
• What it changes: The chosen deliveries show chosen as their Trigger in Webhooks > Deliveries, and an edited payload edited. Your rules stay as they are; the dialog's rules link opens them in a new tab.
• Links to: Webhook rules.
• Same action elsewhere: REST POST /api/v1/samples/{kind}, CLI sendmock sample, MCP sendmock_sample_send
• Same action elsewhere: REST POST /api/v1/webhooks/rules/match, CLI sendmock webhook rule match, MCP sendmock_webhook_rule_match

When the data cannot loadCopy Anchor Link

60. Could not load verifications. Try againCopy Anchor Link

Message.

• What it does: Shown when the verifications could not be loaded.
• Errors: Check SendMock is running, then press Try again.

61. Could not load verifications.Copy Anchor Link

Text.

• What it does: The message inside the alert.

62. Try againCopy Anchor Link

Button.

• What it does: Loads the verifications again.
• Same action elsewhere: REST GET /api/v1/verify, CLI sendmock verify list, MCP sendmock_verify_list