Update Required for AutoEmbed Multi-Language Provider API Endpoint and Encrypted Response Handling #6
Description
Description:
The AutoEmbed multi-language provider has recently changed its API endpoint and response format, which requires an update to the existing integration. The new endpoint structure and the encrypted nature of the response pose a challenge for continued video source retrieval.
New Endpoint: The new endpoint to retrieve video sources is: https://hin.autoembed.cc/api/getVideoSource?type=movie&id={id}
Replace {id} with the movie ID for the video request.
Response Format: The response from the new endpoint includes an encryptedData field:
{"encryptedData":"0ac9f94c21f67907dce3fc919223246d:4b77692addc9988af9be06808b24d44d2a55900384b65a2defd9135eb13b36a42cb371723312aa3ad1c5ddcfcd083466342654b66db1341700accd5457f0d32575b14a82772a897afd9b359cf89af1191b186ee6ec34961369073de2f653e8ea42a3399307bc034d784557a77887db0476e09321a0696b74aaf08834d5430ad1797cb1968d01c8daa1a1ea6f92c9ed1794a0fb9713069c1c2d873fe078adab1b762c8f3d723c60357ddfef0a82d6e96a0dbdaa98f6c3c5446169e964df61e3162e3604da23dfc69a0d4f4fcce995b2712e6498d500ad3b2345a53caf4abff915ef3ad3f6119556afee1433b79d310999491fbdc663cc12345f61613b8741587853c4063dd38a1b6c92a09599b8e2ab004ff7e70cefab9abfb7054f37f09e8d5540b13829fe45e01b7950f39d3e5cbab0da967fb1ab9f3cb3965bbad55e41cb23f0e888ab8869a1baf0811c9ff9526bc666c066df173215092ec1b3954d214f2f3909fe6b82f1810253017527603656482c554eee69fd3a2b0b51d4405970b278530b703f91f958031a22bcbef19aaf8a774cbe4c1a9065e66eb715032708de0540f609ceabf370b7f6b2dbd18fa36af69d37cfccce7e3cbe7eaa0930a2687b382d5a1a68509ac427dcc5ded11914986ef4c611905c3624f6a02031ece9327f39a6707d74e0f93b22ab5fd6626415726224b840096b5d56a0a34c5059fff9f25970a1a3cefdd032f1881e1141bd2237130488c5fc8ab55771bc4c3cb3cb884851e3789169f19960caf3406bf8d16b0839260600673f8dcb2e785cee19c97088e8b783b204ea93958f790c5da47fa49871cf12fe7a3c4afba5920cbb8d9ca0659d830fbeea33d5aa38c75732f50d9acb780740777445b75b78de038b7fe971084cc5a2e0c3abda8a34204bf5732927a621d060a9a03d12ae523e9f3ead84bee85b33d3591e2307de644c58e3a7074665fd6346fc78130b7841774f54e05c1c87e6aff78cae912cccc46eae822a4c73bc74cf90b3fe45a5c0ace24a75a3b1faf2ab10ed7c3fbf21789ab33f8f1a2d78cc7a"}Suggested Solution:
- Update the API integration to accommodate the new endpoint and ensure it handles the encrypted data response correctly.
- Investigate decryption methods or request additional documentation from the provider if needed.
- Consider evaluating other providers instead AutoEmbed if the current provider's encryption is too complex to integrate with.