Add the ability to roster from a registration via the API

When using the Roster Players Create API to create a new record in SportsEngine (roster a player) from an integrated service, the record is not created using the specific registration even if persona_id is passed. The API already accepts persona_id which is derived from a survey, so if persona_id is present, the roster_players create call should preform the same as if the SportsEngine Admin was performing the function from SportsEngine. 

As is, the functionality severely limits our API users because the rostering is not complete.

  • Dan Bartlett
  • Nov 6 2017
  • Future consideration
Frequency Weekly
Which sport(s) does this apply to: Basketball, Football, Lacrosse, Ice Hockey, Soccer, Not Sport Specific, Baseball, Softball
Organization type Other
  • Attach files
  • Dan Bartlett commented
    November 06, 2017 23:20

    Wanted to add that this functionality is being used at where coaches can import players and teams from SportsEngine, hold a draft to form the teams at OnlineDraft, and then return the draft results to SportsEngine to create rosters. Having full rostering at this last step would greatly enhance the whole process of forming teams via a draft and then adding players to correct teams/rosters.

  • Mike Weger commented
    November 07, 2017 01:37

    We have used online draft for our younger grades draft and see it as a key resource for picking and rostering our 1200 players but can’t move forward with it if we can’t correct the API issue.   We are dead in the water and moving back to our old method until this is fixed as addressed between Online Draft and Sports engine.   Mike Weger LSJBA President

  • Tom Wisnasky commented
    November 08, 2017 04:06

    Very efficient way to bring 1000+ kids across multiple grade levels (3rd-12th) within 2 league types (rec vs comp).  Will be a huge time saver for our volunteer staff.  

    Tom Wisnasky

    LSJBA Vice President

  • Carl Rendell commented
    December 28, 2017 21:13

    Dan - I have a product which is about to be released which performs rostering via drag and drop as well as after a completed draft. Using persona_id to place the players works fine, and then I write the team and league back to the fields in the survey for reporting. It's two steps, but works fine for me.