pushresume / backend Goto Github PK

• If user try log-in with already exist JWT-token (request with Authorization header), this token is valid and provider authorization is success - new account "stick" to current user

• User's resume list returns objects, that contains properties provider and resume:

    [
      {
        "provider": "provider_1",
        "resume": [ { ... }, { ... } ]
      },
      {
        "provider": "provider_2",
        "resume": [ { ... }, { ... } ]
      }
    ]
  

If client version less than required, then requests cannot be processed and client need to be updated.
This might help with update mobile clients.

• client send self version with every request
• if client not supported, server returns HTTP error
• client handle this error - "Please, update your app"

Opportunity of send notifications on success or failed operations with user token or resume update

• notification channels
• notification types
• verify channels with OTP or hyperlink
• user may enabled/disable channels or notification types