{"pattern":"(\\w+)@(\\w+)\\.com","flags":"g","matched":true,"count":2,"matches":[{"match":"[email protected]","index":0,"groups":["ana","acme"],"named":null},{"match":"[email protected]","index":14,"groups":["bob","corp"],"named":null}]}
curl --location --request GET 'https://zylalabs.com/api/13159/regular+expression+tester+api/26705/test+regular+expression' --header 'Authorization: Bearer YOUR_API_KEY'
Después de registrarte, a cada desarrollador se le asigna una clave de acceso a la API personal, una combinación única de letras y dígitos proporcionada para acceder a nuestro endpoint de la API. Para autenticarte con el Regular Expression Tester API simplemente incluye tu token de portador en el encabezado de Autorización.
| Encabezado | Descripción |
|---|---|
Autorización
|
Requerido
Debería ser Bearer access_key. Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito.
|
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
(Ahorra 2 meses pagando anualmente 🎉)
Empresas líderes confían en nosotros
Run regular expressions safely, even ones you do not trust. Every pattern is evaluated in an isolated worker with a hard time limit, so catastrophic backtracking is stopped cleanly instead of hanging your servers.
Useful for regular expression playgrounds and teaching tools, validating user supplied patterns before saving them, extracting fields from logs and documents, and debugging patterns in delivery pipelines.
The Test Regular Expression endpoint returns data indicating whether the regex matched the input text, the total match count, and detailed match information including matched text, positions, capture groups, and named groups.
Key fields in the response include "pattern" (the regex used), "flags" (regex flags), "matched" (boolean indicating a match), "count" (number of matches), and "matches" (an array of match details including "match", "index", "groups", and "named").
The response data is structured as a JSON object. It contains the regex pattern and flags, a boolean for match status, a count of matches, and an array of match objects, each detailing the matched text, its position, and any capture or named groups.
The endpoint provides information on whether the regex matched the input, the number of matches found, and detailed match data including the matched text, its position in the input, and any capture or named groups.
Los usuarios pueden personalizar sus solicitudes especificando el patrón regex el texto de entrada y las banderas opcionales como 'g' para coincidencias globales en los parámetros de consulta de la solicitud GET al punto final
Los casos de uso típicos incluyen validar patrones de regex proporcionados por el usuario extraer campos específicos de registros o documentos depurar patrones de regex y crear espacios de juego de regex interactivos con fines educativos
Users can utilize the returned data by analyzing the "matches" array to extract relevant information, such as using capture groups for further processing or displaying matched results in user interfaces.
Standard data patterns include simple matches like email addresses or phone numbers, as well as more complex patterns involving multiple capture groups. Users should expect variations in match counts based on the input text and regex complexity.