### eRecht24 API Server Information Source: https://api-docs.e-recht24.dev/v1/index Details about the eRecht24 API server, including its base path and authorization endpoint. ```APIDOC Servers /v1 - eRecht24 Rechtstexte-API server Authorize ``` -------------------------------- ### Client Management API Source: https://api-docs.e-recht24.dev/index Provides endpoints for managing registered clients, including listing, registering, updating, and deleting clients. Also includes functionality to send test push notifications. ```APIDOC GET /clients Description: List registered clients POST /clients Description: Register client for push notifications PUT /clients/{client_id} Description: Update client information Parameters: client_id: The ID of the client to update DELETE /clients/{client_id} Description: Delete client Parameters: client_id: The ID of the client to delete POST /clients/{client_id}/testPush Description: Send a push notification for development Parameters: client_id: The ID of the client to send a test push notification to ``` -------------------------------- ### Apache License 2.0 Boilerplate Source: https://api-docs.e-recht24.dev/LICENSES This section provides the boilerplate text required to apply the Apache License to your project. It includes placeholders for copyright year and owner, and specifies the terms under which the software can be used, modified, and distributed. ```plaintext Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ``` -------------------------------- ### Client Management API Source: https://api-docs.e-recht24.dev/v1/index Manage registered clients for push notifications. Includes operations to list, register, update, and delete clients, as well as send test push notifications. ```APIDOC GET /clients Description: List registered clients. POST /clients Description: Register client for push notifications. PUT /clients/{client_id} Description: Update client information. Parameters: client_id: The ID of the client to update. DELETE /clients/{client_id} Description: Delete client. Parameters: client_id: The ID of the client to delete. POST /clients/{client_id}/testPush Description: Send a push notification for development. Parameters: client_id: The ID of the client to send the test push notification to. ``` -------------------------------- ### Slim Token Authentication Source: https://api-docs.e-recht24.dev/LICENSES This section details the MIT License as applied to Slim Token Authentication, a project by Dyorg Almeida. It outlines the permissions granted for using, copying, modifying, and distributing the software. ```plaintext Copyright (c) 2016-2017 Dyorg Almeida Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ``` -------------------------------- ### Apache License 2.0 Source: https://api-docs.e-recht24.dev/LICENSES The Apache License, Version 2.0, provides a permissive open-source license that grants users broad rights to use, modify, and distribute software. It includes definitions, grant of copyright and patent licenses, and conditions for use. ```text Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. ``` -------------------------------- ### eRecht24 Rechtstexte-API v1 OpenAPI Specification Source: https://api-docs.e-recht24.dev/v1/index The OpenAPI 3 specification for the eRecht24 Rechtstexte-API v1, detailing available endpoints, request/response formats, and authentication methods. ```APIDOC OAS3 [ //api.e-recht24.dev/v1openapi.json ](https://api.e-recht24.dev/v1openapi.json) ``` -------------------------------- ### Messages API Source: https://api-docs.e-recht24.dev/v1/index Fetch messages from eRecht24.de. ```APIDOC GET /message Description: Fetch message from eRecht24.de. ``` -------------------------------- ### Handling Push Notifications Source: https://api-docs.e-recht24.dev/index The process a client must follow after receiving a push notification from eRecht24. This includes secret verification, status code responses, and pulling updated content. ```APIDOC 1. Check the `erecht24_secret` 2. If the received secret equals the stored secret, return http status code 200, otherwise a suited error status code. 3. Pull message, imprint, privacy policy or privacy policy for social media In case of `'erecht24_type'='ping'` answer with http status code 200 and json message `{ 'message' : 'pong' }` ``` -------------------------------- ### Redistribution Conditions Source: https://api-docs.e-recht24.dev/LICENSES Details the conditions under which the Work or Derivative Works can be reproduced and distributed. This includes requirements for providing the license, indicating modifications, retaining notices, and handling NOTICE files. ```APIDOC Redistribution: Conditions: - Provide a copy of this License to recipients. - Mark modified files with prominent notices of changes. - Retain copyright, patent, trademark, and attribution notices from the original Work in Derivative Works. - Include a readable copy of attribution notices from the NOTICE file in Derivative Works, in specified locations. Modifications: - Users may add their own copyright statements to modifications. - Additional or different license terms can be provided for modifications, as long as they comply with the original License. ``` -------------------------------- ### eRecht24 API v2 OpenAPI Specification Source: https://api-docs.e-recht24.dev/index The OpenAPI 3 specification for the eRecht24 API v2, detailing available endpoints, request/response formats, and authentication methods. ```APIDOC OAS3 [ //api.e-recht24.dev/v2openapi.json?v=202204191032 ](https://api.e-recht24.dev/v2openapi.json?v=202204191032) ``` -------------------------------- ### API Schemas Source: https://api-docs.e-recht24.dev/v1/index Defines the data structures used by the eRecht24 API, including client, legal documents, messages, and error schemas. ```APIDOC Schemas: client imprint privacyPolicy error error401 error422 error503 privacyPolicySocialMedia message message204 ``` -------------------------------- ### Push Notifications API Source: https://api-docs.e-recht24.dev/v1/index Send push notifications to registered clients based on the specified type. ```APIDOC POST /push/{type} Description: Send a push notification to registered clients. Parameters: type: The type of push notification to send. ``` -------------------------------- ### Push Notifications API Source: https://api-docs.e-recht24.dev/index Endpoint for sending push notifications to registered clients. ```APIDOC POST /push/{type} Description: Send a push notification to registered clients. Parameters: type: The type of push notification to send ``` -------------------------------- ### Legal Document Push Notification Handling Source: https://api-docs.e-recht24.dev/index Specific steps for handling push notifications related to legal documents. This includes validating the document type and checking the data source management. ```APIDOC 1. Check wether its a valid legal type and return http status code 400 in case it isnt. 2. If the data source of the legal text is set to be managed locally by the client, return http status code a 422. 3. Pull the content and either respond with http status code 200 if the pull was successfull. Otherwise respond with 400. ``` -------------------------------- ### Guzzle PHP HTTP client License Source: https://api-docs.e-recht24.dev/LICENSES This describes the license for Guzzle, a popular PHP HTTP client. It grants broad permissions for use, modification, and distribution, with the standard disclaimer of warranty. ```plaintext Copyright (c) 2011-2018 Michael Dowling, https://github.com/mtdowling Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ``` -------------------------------- ### API Schemas and Status Codes Source: https://api-docs.e-recht24.dev/index Defines common API response schemas and HTTP status codes used across the e-recht24.dev API. ```APIDOC Schemas: client imprint privacyPolicy privacyPolicySocialMedia message Error Status Codes: 400 401 403 404 409 422 496 497 498 503 Specific Error Schemas: 400-client 404-imprint 404-privacy-policy 404-privacy-policy-social-media Success Status Codes: 204-message ``` -------------------------------- ### MIT License Source: https://api-docs.e-recht24.dev/LICENSES The MIT License is a permissive free software license originating at the Massachusetts Institute of Technology in the US. It allows software to be freely used, modified, and distributed. ```plaintext Copyright (c) [year] [copyright holders] Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ``` -------------------------------- ### Messages API Source: https://api-docs.e-recht24.dev/index API endpoint for fetching messages from e-recht24.de. ```APIDOC GET /message Description: Fetch message from eRecht24.de ``` -------------------------------- ### Push Notification Response Structure Source: https://api-docs.e-recht24.dev/v1/index The expected JSON structure when a client receives a push notification from the eRecht24 API. This includes the secret for verification and the type of notification. ```APIDOC { 'erecht24_secret' : 'varchar128', 'erecht24_type' : 'ping' or 'message' or 'imprint' or 'privacyPolicy' or 'privacyPolicySocialMedia' } ``` -------------------------------- ### Legal Documents API Source: https://api-docs.e-recht24.dev/index Endpoints for retrieving various legal documents provided by e-recht24.de, including imprint and privacy policy information. ```APIDOC GET /imprint Description: Show imprint GET /privacyPolicy Description: Show privacy policy GET /privacyPolicySocialMedia Description: Show privacy policy information for social media ``` -------------------------------- ### Legal Documents API Source: https://api-docs.e-recht24.dev/v1/index Retrieve legal documents from eRecht24. This includes the imprint, privacy policy, and privacy policy information for social media. ```APIDOC GET /imprint Description: Show imprint. GET /privacyPolicy Description: Show privacy policy. GET /privacyPolicySocialMedia Description: Show privacy policy information for social media. ``` -------------------------------- ### Ping Notification Response Source: https://api-docs.e-recht24.dev/v1/index The expected JSON response when a client receives a 'ping' type push notification. The client should respond with a 'pong' message. ```APIDOC { 'message' : 'pong' } ``` -------------------------------- ### Push Notification Response Structure Source: https://api-docs.e-recht24.dev/index The structure of the response received when a client requests a push notification from the eRecht24 API. This includes the secret, type of notification, and potential data. ```APIDOC { 'erecht24_secret' : 'varchar128', 'erecht24_type' : 'ping' or 'message' or 'imprint' or 'privacyPolicy' or 'privacyPolicySocialMedia' } ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.